From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Lechner Subject: Re: [PATCH 2/3] bluetooth: hci_ll: add constant for vendor-specific command Date: Thu, 7 Dec 2017 15:29:02 -0600 Message-ID: <55fff19a-c30f-88f0-afb2-6c0b9bad25a7@lechnology.com> References: <1512357682-8911-1-git-send-email-david@lechnology.com> <1512357682-8911-3-git-send-email-david@lechnology.com> <5C65FB74-D7FD-4653-993A-5A68AD844A41@holtmann.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: devicetree , "open list:BLUETOOTH DRIVERS" , Rob Herring , Mark Rutland , "Gustavo F. Padovan" , Johan Hedberg , netdev@vger.kernel.org, linux-kernel@vger.kernel.org To: Marcel Holtmann Return-path: In-Reply-To: <5C65FB74-D7FD-4653-993A-5A68AD844A41@holtmann.org> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.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 >> --- >> 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?