From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/3] emulator: Fix extended advertising report types
Date: Wed, 07 Oct 2026 18:40:06 +0000 [thread overview]
Message-ID: <179139840653.3650240.14235783377943488144.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261005162117.4606-1-kevin@simpleble.org>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 5 Oct 2026 09:21:14 -0700 you wrote:
> btdev sends the wrong Event_Type in two of the LE Extended Advertising
> Reports it generates for an advertising set:
>
> - the scan response to non-legacy scannable advertising is reported
> with Event_Type 0x0000 instead of 0x000a
> - with more than one active scanner, every scanner after the first gets
> the advertisement reported as a scan response
>
> [...]
Here is the summary with links:
- [BlueZ,1/3] emulator: Remove unused le_ext_adv_type
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=28cfa93135d4
- [BlueZ,2/3] emulator: Fix extended scan response Event_Type
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=11f99edc26c7
- [BlueZ,3/3] emulator: Fix report type after a scan response
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=73d7f86a117a
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-10-07 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 16:21 [PATCH BlueZ 0/3] emulator: Fix extended advertising report types Kevin Dewald
2026-10-05 16:21 ` [PATCH BlueZ 1/3] emulator: Remove unused le_ext_adv_type Kevin Dewald
2026-10-05 20:12 ` emulator: Fix extended advertising report types bluez.test.bot
2026-10-05 16:21 ` [PATCH BlueZ 2/3] emulator: Fix extended scan response Event_Type Kevin Dewald
2026-10-05 16:21 ` [PATCH BlueZ 3/3] emulator: Fix report type after a scan response Kevin Dewald
2026-10-07 18:40 ` 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=179139840653.3650240.14235783377943488144.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.org \
--cc=linux-bluetooth@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 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.