From: Brian Norris <briannorris@chromium.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
devicetree@vger.kernel.org,
Linux Bluetooth mailing list <linux-bluetooth@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Rob Herring <robh+dt@kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Rajat Jain <rajatja@google.com>,
Matthias Kaehlcke <mka@chromium.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs
Date: Fri, 22 Feb 2019 14:10:57 -0800 [thread overview]
Message-ID: <CA+ASDXOFTYmXHw6DD6f3P-0DfyKGZUt9MANEYZXfBBkiXqikYQ@mail.gmail.com> (raw)
In-Reply-To: <5efc9f02-eeb8-78cc-0f11-13e0010efd46@arm.com>
On Fri, Feb 22, 2019 at 1:57 PM Robin Murphy <robin.murphy@arm.com> wrote:
> On 2019-02-22 12:34 am, Brian Norris wrote:
> > + "usb0cf3,e300" (Qualcomm QCA6174A)
> > + "usb04ca,301a" (Qualcomm QCA6174A (Lite-On))
>
> Nit: the USB device binding states that those leading zeroes in the VIDs
> should be suppressed.
Ah, thanks. Didn't notice that part. I'll remove the zeroes and resend.
Brian
next prev parent reply other threads:[~2019-02-22 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 0:34 [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties Brian Norris
2019-02-22 0:34 ` [PATCH 2/3] dt-bindings: net: btusb: add QCA6174A IDs Brian Norris
2019-02-22 18:05 ` Matthias Kaehlcke
2019-02-22 21:57 ` Robin Murphy
2019-02-22 22:10 ` Brian Norris [this message]
2019-02-22 0:34 ` [PATCH 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node Brian Norris
2019-02-22 18:27 ` Matthias Kaehlcke
2019-02-22 23:16 ` Rajat Jain
2019-02-22 18:04 ` [PATCH 1/3] Bluetooth: btusb: add QCA6174A compatible properties Matthias Kaehlcke
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=CA+ASDXOFTYmXHw6DD6f3P-0DfyKGZUt9MANEYZXfBBkiXqikYQ@mail.gmail.com \
--to=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=heiko@sntech.de \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=marcel@holtmann.org \
--cc=mka@chromium.org \
--cc=rajatja@google.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).