[roll] Roll fuchsia [netstack3] Introduce split-crate lock order

Introduce new traits which allow lock levels to be defined away from the
state that holds the locks.

This enables the current core crate split plan of defining the state in
the split crates so we can freely access it in tests, and only define
the lock levels in the final core integration crate.

Original-Fixed: 339655033
Original-Bug: 340341540

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1046308
Original-Revision: 82b7bba7af7a63ece7ba1d95002e9c7eb6fbebdf
GitOrigin-RevId: 46031b27b0c4678d214d2c1818ef0c10db8e7608
Change-Id: I2837e32bf1e5fba69c03087f6e63d82ab4f3e66d
1 file changed
tree: f8e963eef15331aa7aef5faf9fde3f498ad6375c
  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.