From: patchwork-bot+bluetooth@kernel.org
To: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
Cc: marcel@holtmann.org, luiz.dentz@gmail.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, amitkumar.karwar@nxp.com,
sherry.sun@nxp.com, ziniu.wang_1@nxp.com,
johan.korsnes@remarkable.no, kristian.krohn@remarkable.no,
manjeet.gupta@nxp.com
Subject: Re: [PATCH v7 1/2] dt-bindings: net: bluetooth: nxp: Add support to set BD address
Date: Thu, 06 Mar 2025 21:00:54 +0000 [thread overview]
Message-ID: <174129485427.1775969.5271390106327673978.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250303112752.7292-1-neeraj.sanjaykale@nxp.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 3 Mar 2025 16:57:51 +0530 you wrote:
> Allow user to set custom BD address for NXP chipsets.
>
> Signed-off-by: Neeraj Sanjay Kale <neeraj.sanjaykale@nxp.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> v2: Add allOf and unevaluatedProperties: false (Krzysztof)
> v3: Drop local-bd-address: true (Krzysztof)
>
> [...]
Here is the summary with links:
- [v7,1/2] dt-bindings: net: bluetooth: nxp: Add support to set BD address
https://git.kernel.org/bluetooth/bluetooth-next/c/cd4886af1930
- [v7,2/2] Bluetooth: btnxpuart: Add support to set BD address
(no matching commit)
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:[~2025-03-06 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 11:27 [PATCH v7 1/2] dt-bindings: net: bluetooth: nxp: Add support to set BD address Neeraj Sanjay Kale
2025-03-03 11:27 ` [PATCH v7 2/2] Bluetooth: btnxpuart: " Neeraj Sanjay Kale
2025-03-03 11:54 ` [v7,1/2] dt-bindings: net: bluetooth: nxp: " bluez.test.bot
2025-03-06 21: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=174129485427.1775969.5271390106327673978.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=amitkumar.karwar@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan.korsnes@remarkable.no \
--cc=kristian.krohn@remarkable.no \
--cc=krzk+dt@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=manjeet.gupta@nxp.com \
--cc=marcel@holtmann.org \
--cc=neeraj.sanjaykale@nxp.com \
--cc=robh@kernel.org \
--cc=sherry.sun@nxp.com \
--cc=ziniu.wang_1@nxp.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