[roll] Roll fuchsia [netstack] Lock when accessing protected fields Although not strictly necessary becuase there is no possibility of concurrent access or races with the accesses updated in this change, we should always follow the pattern of holding a lock `x.mu` when accessing fields `x.mu.fieldX` for readability and avoiding confusion. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/891313 Original-Revision: 1937bf518aa7e19b1d508d22c381010e285a7233 GitOrigin-RevId: cc18cf9657453e631489e6620ed0e5353a5a741d Change-Id: I02780e20ee71c2bf8ec6d984aa3d8469c221b03e
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.