From: Harish Bandi <c-hbandi@codeaurora.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
hemantg@codeaurora.org, linux-arm-msm@vger.kernel.org,
bgodavar@codeaurora.org, anubhavg@codeaurora.org,
devicetree@vger.kernel.org, mark.rutland@arm.com,
robh+dt@kernel.org
Subject: Re: [PATCH v6 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip WCN3998
Date: Fri, 29 Mar 2019 10:08:45 +0530 [thread overview]
Message-ID: <273d6b53cec219cb1c1a3432da331c46@codeaurora.org> (raw)
In-Reply-To: <20190327172905.GE112750@google.com>
Hi Matthias,
On 2019-03-27 22:59, Matthias Kaehlcke wrote:
> On Wed, Mar 27, 2019 at 05:58:43PM +0530, Harish Bandi wrote:
>> This patch enables regulators for the Qualcomm Bluetooth WCN3998
>> controller.
>
> I commented on this on v3, but you didn't update it:
>
> No, it doesn't.
>
> The next version should probably say something like "Add compatible
> string for the Qualcomm WCN3998 Bluetooth controller".
>
[Harish] - will take care in next version.
> Thanks
>
> Matthias
next prev parent reply other threads:[~2019-03-29 4:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 12:28 [PATCH v6 0/2] Enable Bluetooth functionality for WCN3998 Harish Bandi
2019-03-27 12:28 ` [PATCH v6 1/2] Bluetooth: hci_qca: Added support " Harish Bandi
2019-03-27 16:46 ` Balakrishna Godavarthi
2019-03-27 16:56 ` Matthias Kaehlcke
2019-03-29 4:40 ` Harish Bandi
2019-03-28 21:05 ` kbuild test robot
2019-03-28 21:23 ` Matthias Kaehlcke
2019-03-29 4:42 ` Harish Bandi
2019-07-05 7:33 ` Doubt/issue in hci_dev_do_close Harish Bandi
2019-07-06 10:22 ` Marcel Holtmann
2019-04-01 16:16 ` [PATCH v6 1/2] Bluetooth: hci_qca: Added support for WCN3998 Marc Gonzalez
2019-03-27 12:28 ` [PATCH v6 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip WCN3998 Harish Bandi
2019-03-27 17:29 ` Matthias Kaehlcke
2019-03-29 4:38 ` Harish Bandi [this message]
2019-04-01 12:39 ` Harish Bandi
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=273d6b53cec219cb1c1a3432da331c46@codeaurora.org \
--to=c-hbandi@codeaurora.org \
--cc=anubhavg@codeaurora.org \
--cc=bgodavar@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=hemantg@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@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 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).