[roll] Roll fuchsia [superproject] Roll third_party/pigweed pw_rpc: Add function for yielding the RPC lock in C++ Upcoming CLs will require threads to yield the RPC lock while waiting for a different thread to finish executing an RPC callback. - Add a config option for selecting how to yield (busy loop, pw::this_thread::sleep_for(), pw::this_thread::yield()). - Add dependencies on pw_thread if backends are defined. - Have the pw_rpc:disable_global_mutex config select the busy loop yield approach, since platforms with the mutex disabled either do not support threading or exclusively use RPC from one thread. - Disable the RPC lock on a few platforms with no RTOS. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/126751 Original-Revision: 8050957fa9ef835ede9aa63671ac805260dc979b GitOrigin-RevId: 951fb2275bee5ee8818cbf4063f9830ac1f66bb5 Roller-URL: https://ci.chromium.org/b/8791113093823904641 CQ-Do-Not-Cancel-Tryjobs: true Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/792549 Original-Revision: b30fa50a10445fa499775a29b15cee82d134a6c6 Change-Id: Ie4dffd84a159333b09bfdc63aeaa6c2c3f62d11d
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.