[roll] Roll fuchsia [bt][sm] Use PairingChannel in SC Phase 2 Stage 1 classes Previously, the Secure Connections Phase 2 Stage 1 classes used a constructor-provided callback to send SMP messages, which directly accessed the SM L2CAP channel. These classes now use the PairingChannel class instead, which provides convenience methods so that clients don't have to build ByteBuffers directly. This enables the removal of direct access to the underlying L2CAP channel in SM, ensuring that all message sending goes through the PairingChannel. Original-Bug: 53705 Test: Refactor; run `fx test bt-host-unittests` to verify. Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/457015 Original-Revision: d4f3a9978ca6862ffff8ccc1c219b371d20de8ed GitOrigin-RevId: 5c0a245666c25f615425c527f21074b5a1cd843e Change-Id: I068a5578a19feefe591cc48c45f6692ee874c18a
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.