From: patchwork-bot+bluetooth@kernel.org
To: Sven Peter via B4 Relay <devnull+sven.svenpeter.dev@kernel.org>
Cc: marcan@marcan.st, alyssa@rosenzweig.io, marcel@holtmann.org,
luiz.dentz@gmail.com, johan.hedberg@gmail.com,
luiz.von.dentz@intel.com, asahi@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, j@jannau.net, sven@svenpeter.dev
Subject: Re: [PATCH] Bluetooth: Add quirk to ignore reserved PHY bits in LE Extended Adv Report
Date: Wed, 15 May 2024 19:50:29 +0000 [thread overview]
Message-ID: <171580262946.22700.3070812147966702981.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240515-btfix-v1-1-d88caf3d5a3f@svenpeter.dev>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 15 May 2024 18:02:58 +0000 you wrote:
> From: Sven Peter <sven@svenpeter.dev>
>
> Some Broadcom controllers found on Apple Silicon machines abuse the
> reserved bits inside the PHY fields of LE Extended Advertising Report
> events for additional flags. Add a quirk to drop these and correctly
> extract the Primary/Secondary_PHY field.
>
> [...]
Here is the summary with links:
- Bluetooth: Add quirk to ignore reserved PHY bits in LE Extended Adv Report
https://git.kernel.org/bluetooth/bluetooth-next/c/9dc8ac15ca51
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:[~2024-05-15 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 18:02 [PATCH] Bluetooth: Add quirk to ignore reserved PHY bits in LE Extended Adv Report Sven Peter via B4 Relay
2024-05-15 19: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=171580262946.22700.3070812147966702981.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=alyssa@rosenzweig.io \
--cc=asahi@lists.linux.dev \
--cc=devnull+sven.svenpeter.dev@kernel.org \
--cc=j@jannau.net \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcan@marcan.st \
--cc=marcel@holtmann.org \
--cc=stable@vger.kernel.org \
--cc=sven@svenpeter.dev \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).