From: patchwork-bot+bluetooth@kernel.org
To: Zhao Li <enderaoelyther@gmail.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: MGMT: Retain the selected legacy advertising schedule ID
Date: Thu, 19 Nov 2026 18:50:08 +0000 [thread overview]
Message-ID: <179511420877.3743161.3171281660123127409.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261119112359.34543-1-enderaoelyther@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 19 Nov 2026 19:23:59 +0800 you wrote:
> Updating the currently advertised legacy instance can schedule that same
> instance again instead of the next selected instance. Add Advertising
> stores the selected ID in the original request after mgmt_pending_new() has
> copied it, so the queued callback still reads the requested ID. Add
> Extended Advertising Data never passes the selected ID to its callback.
>
> Pass the selected ID to both callbacks in the pending command's user
> data, and keep the request ID for the replies and completion cleanup.
> Extended advertising controllers do not rotate instances in software, so
> keep scheduling the requested instance there, as both callbacks do now,
> without cancelling the rotation timeout or looking up the next one.
>
> [...]
Here is the summary with links:
- Bluetooth: MGMT: Retain the selected legacy advertising schedule ID
https://git.kernel.org/bluetooth/bluetooth-next/c/5052141b19fe
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-19 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 11:23 [PATCH] Bluetooth: MGMT: Retain the selected legacy advertising schedule ID Zhao Li
2026-11-19 17:37 ` bluez.test.bot
2026-11-19 18:50 ` 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=179511420877.3743161.3171281660123127409.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=enderaoelyther@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox