From: patchwork-bot+bluetooth@kernel.org
To: Marek Vasut <marex@denx.de>
Cc: linux-bluetooth@vger.kernel.org, pbrobinson@gmail.com,
robh@kernel.org, linus.walleij@linaro.org,
hakan.jansson@infineon.com, krzysztof.kozlowski@linaro.org,
luiz.von.dentz@intel.com, marcel@holtmann.org,
robh+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding
Date: Wed, 02 Nov 2022 21:00:15 +0000 [thread overview]
Message-ID: <166742281569.25440.9584575292031556354.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221102164705.14538-1-marex@denx.de>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 2 Nov 2022 17:47:04 +0100 you wrote:
> CYW4373A0 is a Wi-Fi + Bluetooth combo device from Cypress.
> This chip is present e.g. on muRata 2AE module. Extend the
> binding with its DT compatible.
>
> Acked-by: Rob Herring <robh@kernel.org>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Marek Vasut <marex@denx.de>
>
> [...]
Here is the summary with links:
- [v2,1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding
https://git.kernel.org/bluetooth/bluetooth-next/c/0a8d4b84bbd5
- [v2,2/2] Bluetooth: hci_bcm: Add CYW4373A0 support
https://git.kernel.org/bluetooth/bluetooth-next/c/ce52c2f04177
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:[~2022-11-02 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:47 [PATCH v2 1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding Marek Vasut
2022-11-02 16:47 ` [PATCH v2 2/2] Bluetooth: hci_bcm: Add CYW4373A0 support Marek Vasut
2022-11-02 17:33 ` [v2,1/2] dt-bindings: net: broadcom-bluetooth: Add CYW4373A0 DT binding bluez.test.bot
2022-11-02 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=166742281569.25440.9584575292031556354.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hakan.jansson@infineon.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.org \
--cc=marex@denx.de \
--cc=pbrobinson@gmail.com \
--cc=robh+dt@kernel.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 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.