[roll] Roll fuchsia [sysmem] Weak with no usage gets close_weak_asap

This is particularly useful when a client has done
SetWeakOk(for_child_nodes_also=true), but doesn't have any usage of
its own, so doesn't need to set any usage bits and doesn't need any
VMO handles for itself. Despite not receiving any weak VMO handles,
such a client can listen for close_weak_asap and indirectly cause
weak VMO handles to be closed.

BUG: b/284073556
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/933632
Original-Revision: 6872795db0fa0b1357e27781016c236e3ed939c1
GitOrigin-RevId: ecd67ea99bdcb8e174bd9999d5fab46231a87a49
Change-Id: I188412fe27131d398fdd902e7045b9703cbc9f40
1 file changed
tree: cf6fd4a50b197345279fa157b6026bdf4c4ad22e
  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.