[roll] Roll fuchsia [superproject] Roll fuchsia [nxpfmac] Fix deadlock in EAPOL response handling There was an issue with EAPOL response handling where it synchronously acquired a lock that could be held by another call from SME. At the same time the EAPOL response code would block the driver from servicing the SME request. This resulted in a deadlock. The code already performed the EAPOL response call to SME in a separate thread. This change makes sure that the validity check of the SME interface along with holding the lock required for the check also happens in the separate thread. Test: WlanSecurityComplianceABGTest ACTS test Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/745985 Original-Revision: 27f9696a84508539b88ef769d7b04b04bc379fba GitOrigin-RevId: 14db9f4d2d133f10af02c0ce05c704ddd6aa0d64 Roller-URL: https://ci.chromium.org/b/8799398923839168753 CQ-Do-Not-Cancel-Tryjobs: true Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/746290 Original-Revision: 242515cd3459a5614df21eba228b9f21b988e2f8 Change-Id: If77fcfd064c4c902e136258968f3d833916685a3
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.