[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55fff19a-c30f-88f0-afb2-6c0b9bad25a7@lechnology.com>
Date: Thu, 7 Dec 2017 15:29:02 -0600
From: David Lechner <david@...hnology.com>
To: Marcel Holtmann <marcel@...tmann.org>
Cc: devicetree <devicetree@...r.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
"Gustavo F. Padovan" <gustavo@...ovan.org>,
Johan Hedberg <johan.hedberg@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific
command
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@...hnology.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?
Powered by blists - more mailing lists