[roll] Roll fuchsia [sysmem] Permit getting v2 Allocator from v1

This allows connecting to sysmem2 Allocator given only a sysmem(1)
Allocator. This helps in situations where shared lib code is being
updated to sysmem2, but gets created by passing in a sysmem(1)
Allocator, and the shared lib code doesn't necessarily know that it's
ok to connect to sysmem2 instead via /svc, such as when the lib code
is being used in a driver.

BUG: 306258175
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/963656
Original-Revision: 1b1334cf801c7c281718f259dc7960fb4db505f9
GitOrigin-RevId: 208389a50b19eceba16a305bb8e5d1bfae6b05b0
Change-Id: I48b6b7a3f143a5198b9f2ab2c9711c9212d214f6
1 file changed
tree: 47899dd53528146a8ab681dbaa7b274fb5baaaed
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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.