| Message ID | 20250226-leaudio-no-media-v3-1-8f4f93d8a41c@amlogic.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | f4617c531abe2cd263ce3b9ba7ba77dc5859215c |
| Headers | show |
| Series | [bluez,v3] adapter: Prepend the new added device to the adapter devices list | expand |
| Context | Check | Description |
|---|---|---|
| tedd_an/pre-ci_am | success | Success |
| tedd_an/BuildEll | success | Build ELL PASS |
| tedd_an/BluezMake | success | Bluez Make PASS |
| tedd_an/MakeCheck | success | Bluez Make Check PASS |
| tedd_an/MakeDistcheck | success | Make Distcheck PASS |
| tedd_an/CheckValgrind | success | Check Valgrind PASS |
| tedd_an/CheckSmatch | success | CheckSparse PASS |
| tedd_an/bluezmakeextell | success | Make External ELL PASS |
| tedd_an/ScanBuild | success | Scan Build PASS |
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=937918 ---Test result--- Test Summary: CheckPatch PENDING 0.27 seconds GitLint PENDING 0.30 seconds BuildEll PASS 21.89 seconds BluezMake PASS 1575.97 seconds MakeCheck PASS 13.32 seconds MakeDistcheck PASS 169.10 seconds CheckValgrind PASS 220.23 seconds CheckSmatch PASS 291.90 seconds bluezmakeextell PASS 101.46 seconds IncrementalBuild PENDING 0.35 seconds ScanBuild PASS 916.39 seconds Details ############################## Test: CheckPatch - PENDING Desc: Run checkpatch.pl script Output: ############################## Test: GitLint - PENDING Desc: Run gitlint Output: ############################## Test: IncrementalBuild - PENDING Desc: Incremental build with the patches in the series Output: --- Regards, Linux Bluetooth
Hello: This patch was applied to bluetooth/bluez.git (master) by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>: On Wed, 26 Feb 2025 16:52:04 +0800 you wrote: > From: Ye He <ye.he@amlogic.com> > > When the DUT is paired with a mobile phone using RPA multiple times, > multiple device contexts with the same bdaddr will be cached. > When we query the device context through bdaddr, we always get the > context at the head of adapter->devices, but its status is inactive. > > [...] Here is the summary with links: - [bluez,v3] adapter: Prepend the new added device to the adapter devices list https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=f4617c531abe You are awesome, thank you!
diff --git a/src/adapter.c b/src/adapter.c index cbe5b197963a7e07a50f74a697ad3d35f9bc3786..c0d647efdde0d9eab2e27c360c0bfb9fbadeb7ef 100644 --- a/src/adapter.c +++ b/src/adapter.c @@ -5252,7 +5252,7 @@ void device_resolved_drivers(struct btd_adapter *adapter, static void adapter_add_device(struct btd_adapter *adapter, struct btd_device *device) { - adapter->devices = g_slist_append(adapter->devices, device); + adapter->devices = g_slist_prepend(adapter->devices, device); device_added_drivers(adapter, device); }