From: patchwork-bot+bluetooth@kernel.org
To: Weihong Guan <weihong.guan@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ 0/2] Single advertising set in the emulator and mgmt-tester
Date: Mon, 16 Nov 2026 20:00:06 +0000 [thread overview]
Message-ID: <179485920627.3860040.3796894125726226871.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261112023858.892176-1-weihong.guan@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 12 Nov 2026 02:38:56 +0000 you wrote:
> A controller may report a single advertising set (LE Read Number of
> Supported Advertising Sets returns 0x01 to 0xF0). The kernel then gives
> advertising instance 1 handle 0x00, the handle Global Advertising uses
> too, and several places took the instance number for the handle. Those
> were fixed in bluetooth-next by commits daf949c968d4, e7e877bf658a,
> 8b1eff978e66 and 4dce35adafb5, but the emulator always reports three
> sets, so mgmt-tester couldn't see them.
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] emulator: Set the number of advertising sets
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=58e111cc9904
- [BlueZ,2/2] mgmt-tester: Add single advertising set tests
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=923d95d0c2fb
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-16 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 2:38 [PATCH BlueZ 0/2] Single advertising set in the emulator and mgmt-tester Weihong Guan
2026-11-12 2:38 ` [PATCH BlueZ 1/2] emulator: Set the number of advertising sets Weihong Guan
2026-11-12 9:14 ` Single advertising set in the emulator and mgmt-tester bluez.test.bot
2026-11-12 2:38 ` [PATCH BlueZ 2/2] mgmt-tester: Add single advertising set tests Weihong Guan
2026-11-16 20:00 ` 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=179485920627.3860040.3796894125726226871.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=weihong.guan@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox