From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Luca Weiss <luca@z3ntu.xyz>
Cc: linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
devicetree@vger.kernel.org, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 0/5] Wifi & Bluetooth on LG G Watch R
Date: Wed, 23 Feb 2022 22:15:06 -0600 [thread overview]
Message-ID: <YhcGSmd5M3W+fI6c@builder.lan> (raw)
In-Reply-To: <20220216212433.1373903-1-luca@z3ntu.xyz>
On Wed 16 Feb 15:24 CST 2022, Luca Weiss wrote:
> This series adds the BCM43430A0 chip providing Bluetooth & Wifi on the
> LG G Watch R.
>
I picked the dts changes, but would prefer that the other two changes
goes through the BT tree. I see that you haven't copied Marcel on the
dt-binding change though, so please resubmit those two patches together.
Thanks,
Bjorn
> Luca Weiss (5):
> dt-bindings: bluetooth: broadcom: add BCM43430A0
> Bluetooth: hci_bcm: add BCM43430A0
> ARM: dts: qcom: msm8226: Add pinctrl for sdhci nodes
> ARM: dts: qcom: apq8026-lg-lenok: Add Wifi
> ARM: dts: qcom: apq8026-lg-lenok: Add Bluetooth
>
> .../bindings/net/broadcom-bluetooth.yaml | 1 +
> arch/arm/boot/dts/qcom-apq8026-lg-lenok.dts | 98 ++++++++++++++++---
> arch/arm/boot/dts/qcom-msm8226.dtsi | 57 +++++++++++
> drivers/bluetooth/hci_bcm.c | 1 +
> 4 files changed, 144 insertions(+), 13 deletions(-)
>
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-02-24 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 21:24 [PATCH 0/5] Wifi & Bluetooth on LG G Watch R Luca Weiss
2022-02-16 21:24 ` [PATCH 1/5] dt-bindings: bluetooth: broadcom: add BCM43430A0 Luca Weiss
2022-02-22 15:21 ` Linus Walleij
2022-02-25 16:29 ` Rob Herring
2022-02-24 4:15 ` Bjorn Andersson [this message]
2022-02-25 20:19 ` [PATCH 0/5] Wifi & Bluetooth on LG G Watch R Luca Weiss
2022-02-25 21:57 ` Bjorn Andersson
2022-02-24 20:54 ` (subset) " Bjorn Andersson
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=YhcGSmd5M3W+fI6c@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=netdev@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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 NNTP newsgroup(s).