[roll] Roll fuchsia [sysmem] Allow weak v1 child Node when safe

When a parent Node has set for_child_nodes_also=true, the child weak
Node can be v1 despite inability to deliver close_weak_asap to that
v1 child Node, since the parent Node has promised to pay attention to
close_weak_asap on behalf of the child Node.

BUG: b/284073556
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/934352
Original-Revision: 8efe901d217c97caaeb9230c2e7e716f845cedcc
GitOrigin-RevId: 09af68876e9cb8f1893f86d350f6a2160b740144
Change-Id: I24c94ce0e18434c8a47a2d13d47ca26eabb31938
1 file changed
tree: 55939ef56b8bdb1a385d3fdebf3589bfb680b647
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.