[roll] Roll fuchsia [netstack3] Move device configuration to DeviceApi Instead of matching on DeviceId and using SyncCtx directly in freestanding functions, embrace the API struct pattern. Model loopback not supporting NUD configuration through a new trait, DeviceConfigurationContext that CoreCtx implements for both EthernetLinkDevice and LoopbackDevice. Also introduce a `DeviceAnyApi` struct that maintains the ergonomics for bindings dealing with `DeviceId` instead of the domain specific identifiers, following the pattern used in `RoutesAnyApi`. Original-Bug: b/42083910 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/976626 Original-Revision: 4e8b573ed6f15dc7f0dfc3156fbcc3c3afba8258 GitOrigin-RevId: 6d16fc8d58baf28f9523af4e9ff4d5d3fdd62c3b Change-Id: Ib2bc3fa1f7689ed27e67d17526cbcd91df1b72cd
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.