From: patchwork-bot+bluetooth@kernel.org
To: Linus Walleij <linusw@kernel.org>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-bluetooth@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] Use platform Bluetooth addresses on Broadcom UART controllers
Date: Wed, 11 Nov 2026 19:40:17 +0000 [thread overview]
Message-ID: <179442601766.1604530.10253398492524205694.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110-brcm-bcmbt-mac-v1-0-c68003a06f64@kernel.org>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 10 Nov 2026 11:45:25 +0100 you wrote:
> Allow local-bd-address through the common Bluetooth controller binding,
> including its six-byte little-endian representation.
>
> Enable the existing HCI core property.
>
> Absent, unreadable and all-zero properties preserve the existing setup
> path.
>
> [...]
Here is the summary with links:
- [1/2] dt-bindings: bluetooth: brcm: Allow a platform BD address
https://git.kernel.org/bluetooth/bluetooth-next/c/05ad7f2dee07
- [2/2] Bluetooth: hci_bcm: Prefer a valid platform BD address
https://git.kernel.org/bluetooth/bluetooth-next/c/afafcb373fd0
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-11 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 10:45 [PATCH 0/2] Use platform Bluetooth addresses on Broadcom UART controllers Linus Walleij
2026-11-10 10:45 ` [PATCH 1/2] dt-bindings: bluetooth: brcm: Allow a platform BD address Linus Walleij
2026-11-10 18:49 ` Conor Dooley
2026-11-10 10:45 ` [PATCH 2/2] Bluetooth: hci_bcm: Prefer a valid " Linus Walleij
2026-11-11 19: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=179442601766.1604530.10253398492524205694.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=robh@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