From: Rob Herring <robh@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>,
Rajat Jain <rajatja@google.com>,
Robin Murphy <robin.murphy@arm.com>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: net: btusb: add QCA6174A IDs
Date: Tue, 26 Feb 2019 16:32:41 -0600 [thread overview]
Message-ID: <20190226223241.GA2365@bogus> (raw)
In-Reply-To: <20190222225345.69084-2-briannorris@chromium.org>
On Fri, 22 Feb 2019 14:53:44 -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
> ---
> v2:
> * drop leading zeroes from VID
> ---
> Documentation/devicetree/bindings/net/btusb.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Douglas Anderson <dianders@chromium.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthias Kaehlcke <mka@chromium.org>,
Rajat Jain <rajatja@google.com>,
Robin Murphy <robin.murphy@arm.com>,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2 2/3] dt-bindings: net: btusb: add QCA6174A IDs
Date: Tue, 26 Feb 2019 16:32:41 -0600 [thread overview]
Message-ID: <20190226223241.GA2365@bogus> (raw)
In-Reply-To: <20190222225345.69084-2-briannorris@chromium.org>
On Fri, 22 Feb 2019 14:53:44 -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
> ---
> v2:
> * drop leading zeroes from VID
> ---
> Documentation/devicetree/bindings/net/btusb.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Brian Norris <briannorris@chromium.org>
Cc: devicetree@vger.kernel.org, Heiko Stuebner <heiko@sntech.de>,
linux-bluetooth@vger.kernel.org,
Marcel Holtmann <marcel@holtmann.org>,
Brian Norris <briannorris@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Matthias Kaehlcke <mka@chromium.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Rajat Jain <rajatja@google.com>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH v2 2/3] dt-bindings: net: btusb: add QCA6174A IDs
Date: Tue, 26 Feb 2019 16:32:41 -0600 [thread overview]
Message-ID: <20190226223241.GA2365@bogus> (raw)
In-Reply-To: <20190222225345.69084-2-briannorris@chromium.org>
On Fri, 22 Feb 2019 14:53:44 -0800, Brian Norris wrote:
> There are two USB PID/VID variations I've seen for this chip, and I want
> to utilize the 'interrupts' property defined here already.
>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
> ---
> v2:
> * drop leading zeroes from VID
> ---
> Documentation/devicetree/bindings/net/btusb.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-26 22:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 22:53 [PATCH v2 1/3] Bluetooth: btusb: add QCA6174A compatible properties Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-22 22:53 ` [PATCH v2 2/3] dt-bindings: net: btusb: add QCA6174A IDs Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-26 22:32 ` Rob Herring [this message]
2019-02-26 22:32 ` Rob Herring
2019-02-26 22:32 ` Rob Herring
2019-02-22 22:53 ` [PATCH v2 3/3] arm64: dts: rockchip: move QCA6174A wakeup pin into its USB node Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-22 22:53 ` Brian Norris
2019-02-26 9:01 ` [PATCH v2 1/3] Bluetooth: btusb: add QCA6174A compatible properties Marcel Holtmann
2019-02-26 9:01 ` Marcel Holtmann
2019-02-26 13:31 ` Robin Murphy
2019-02-26 13:31 ` Robin Murphy
2019-02-27 7:53 ` Marcel Holtmann
2019-02-27 7:53 ` Marcel Holtmann
2019-02-27 21:34 ` Brian Norris
2019-02-27 21:34 ` Brian Norris
2019-03-26 18:45 ` Brian Norris
2019-03-26 18:45 ` Brian Norris
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=20190226223241.GA2365@bogus \
--to=robh@kernel.org \
--cc=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=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 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.