From: David Lechner <david@lechnology.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: devicetree <devicetree@vger.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Gustavo F. Padovan" <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command
Date: Thu, 7 Dec 2017 15:29:02 -0600 [thread overview]
Message-ID: <55fff19a-c30f-88f0-afb2-6c0b9bad25a7@lechnology.com> (raw)
In-Reply-To: <5C65FB74-D7FD-4653-993A-5A68AD844A41@holtmann.org>
On 12/04/2017 12:23 AM, Marcel Holtmann wrote:
> Hi David,
>
>> This adds a #define for the vendor-specific HCI command to set the
>> baudrate instead of using the bare 0xff36 multiple times.
>>
>> Signed-off-by: David Lechner <david@lechnology.com>
>> ---
>> drivers/bluetooth/hci_ll.c | 10 ++++++++--
>> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> patch has been applied to bluetooth-next tree.
>
I am new to the bluetooth tree, so just to be sure... does this mean I
should not include this patch in v2 of this series since this patch has
been applied?
next prev parent reply other threads:[~2017-12-07 21:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 3:21 [PATCH 0/3] bluetooth: hci_ll: Get MAC address from NVMEM David Lechner
2017-12-04 3:21 ` [PATCH 1/3] dt-bindings: Add optional nvmem MAC address bindings to ti,wlink-st David Lechner
2017-12-04 6:50 ` Marcel Holtmann
2017-12-04 9:54 ` Sergei Shtylyov
2017-12-04 10:09 ` Sergei Shtylyov
2017-12-04 3:21 ` [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command David Lechner
2017-12-04 6:23 ` Marcel Holtmann
2017-12-07 21:29 ` David Lechner [this message]
2017-12-07 21:43 ` Marcel Holtmann
2017-12-04 3:21 ` [PATCH 3/3] bluetooth: hci_ll: Add optional nvmem MAC address source David Lechner
2017-12-04 6:48 ` Marcel Holtmann
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=55fff19a-c30f-88f0-afb2-6c0b9bad25a7@lechnology.com \
--to=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.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).