[roll] Roll fuchsia [netdevice-migration] Make proper use of atomics

The previous usage was inherently racy; incrementing, loading, and
storing separately defeats the purpose of using an atomic. Use a single
add operation instead and modulo the result to determine when to log.

Appease clang-tidy while I'm here.

Original-Fixed: 97178
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/677933
Original-Revision: d8f972e3fc5c299e6b22fcab7e6869c2fef07e9d
GitOrigin-RevId: 1f2e1762fa4590c955a4d0a049c432fa3543a7f7
Change-Id: Ie0aa554d7dad890a274ee3a88e4fe7258abd816b
1 file changed
tree: ce8c02a07b616b071f0578437db23b45186c52a3
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.