[roll] Roll fuchsia [starnix] Drop `MemoryAccessor::vmo_*` methods

This is done since `MemoryAccessor` implementations will make the
decision about whether to use unified aspace or VMO backed usercopy
utilities. For example, `CurrentTask` assumes unified aspaces may be
leveraged whereas `Task` always goes through the VMO.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/976619
Original-Revision: 22f4a107ffbb9765c4e73fe0bc9e06254149b702
GitOrigin-RevId: 4828c434226f51d18e613832479193d5eaaf901e
Change-Id: Ic90cac8ba9ebc3d84eac23f2529d0dd84996af0c
1 file changed
tree: ef87b40e77666bc98ed611dfab45bffcba7cb009
  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.