From: patchwork-bot+bluetooth@kernel.org
To: Marek Vasut <marex@denx.de>
Cc: linux-bluetooth@vger.kernel.org, krzysztof.kozlowski@linaro.org,
davem@davemloft.net, conor+dt@kernel.org, edumazet@google.com,
kuba@kernel.org, krzysztof.kozlowski+dt@linaro.org,
linus.walleij@linaro.org, luiz.dentz@gmail.com,
marcel@holtmann.org, pabeni@redhat.com, robh@kernel.org,
devicetree@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [bluetooth-next PATCH v3] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding
Date: Tue, 30 Apr 2024 14:20:30 +0000 [thread overview]
Message-ID: <171448683042.20667.15080644752869073034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240430010914.110179-1-marex@denx.de>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 30 Apr 2024 03:08:42 +0200 you wrote:
> CYW43439 is a Wi-Fi + Bluetooth combo device from Infineon.
> The Bluetooth part is capable of Bluetooth 5.2 BR/EDR/LE .
> This chip is present e.g. on muRata 1YN module.
>
> Extend the binding with its DT compatible using fallback
> compatible string to "brcm,bcm4329-bt" which seems to be
> the oldest compatible device. This should also prevent the
> growth of compatible string tables in drivers. The existing
> block of compatible strings is retained.
>
> [...]
Here is the summary with links:
- [bluetooth-next,v3] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding
https://git.kernel.org/bluetooth/bluetooth-next/c/25acde2bb2fa
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-04-30 14:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 1:08 [bluetooth-next PATCH v3] dt-bindings: net: broadcom-bluetooth: Add CYW43439 DT binding Marek Vasut
2024-04-30 14:20 ` 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=171448683042.20667.15080644752869073034.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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 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.