All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Ye He via B4 Relay <devnull+ye.he.amlogic.com@kernel.org>
Cc: linux-bluetooth@vger.kernel.org, ye.he@amlogic.com
Subject: Re: [PATCH bluez v3] adapter: Prepend the new added device to the adapter devices list
Date: Wed, 26 Feb 2025 20:30:31 +0000	[thread overview]
Message-ID: <174060183101.836490.15009751272938914519.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250226-leaudio-no-media-v3-1-8f4f93d8a41c@amlogic.com>

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!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-02-26 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-26  8:52 [PATCH bluez v3] adapter: Prepend the new added device to the adapter devices list Ye He
2025-02-26  8:52 ` Ye He via B4 Relay
2025-02-26 10:14 ` [bluez,v3] " bluez.test.bot
2025-02-26 20:30 ` patchwork-bot+bluetooth [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=174060183101.836490.15009751272938914519.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=devnull+ye.he.amlogic.com@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ye.he@amlogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.