[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <C76378A5-AAAF-42A6-BD74-119E4863D813@holtmann.org>
Date: Thu, 7 Dec 2017 22:43:18 +0100
From: Marcel Holtmann <marcel@...tmann.org>
To: David Lechner <david@...hnology.com>
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>,
Network Development <netdev@...r.kernel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific
command
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?
please don’t include already applied patches. Base everything against bluetooth-next tree.
Regards
Marcel
Powered by blists - more mailing lists