Return-Path: From: "Savoy, Pavan" To: "Gustavo F. Padovan" , Marcel Holtmann CC: Greg KH , "pavan-savoy@ti.com" , "linux-bluetooth@vger.kernel.org" , "johan.hedberg@gmail.com" , "linux-kernel@vger.kernel.org" Date: Fri, 8 Oct 2010 02:54:22 +0530 Subject: RE: [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver Message-ID: <19F8576C6E063C45BE387C64729E739404AA21D256@dbde02.ent.ti.com> References: <1286404493-23816-1-git-send-email-pavan-savoy@ti.com> <1286404493-23816-2-git-send-email-pavan-savoy@ti.com> <1286445948.6145.70.camel@aeonflux> <20101007143409.GB14913@kroah.com> <1286464867.6145.148.camel@aeonflux> <20101007175715.GA13602@vigoh> In-Reply-To: <20101007175715.GA13602@vigoh> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 List-ID: Marcel, Gustavo, > -----Original Message----- > From: Gustavo F. Padovan [mailto:pao@profusion.mobi] On Behalf Of Gustavo= F. > Padovan > Sent: Thursday, October 07, 2010 12:57 PM > To: Marcel Holtmann > Cc: Greg KH; pavan-savoy@ti.com; linux-bluetooth@vger.kernel.org; > johan.hedberg@gmail.com; linux-kernel@vger.kernel.org; Savoy, Pavan > Subject: Re: [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver >=20 > * Marcel Holtmann [2010-10-07 17:21:07 +0200]: >=20 > > Hi Greg, > > > > > > > This is the bluetooth protocol driver for the TI WiLink7 chipsets= . > > > > > Texas Instrument's WiLink chipsets combine wireless technologies > > > > > like BT, FM, GPS and WLAN onto a single chip. > > > > > > > > > > This Bluetooth driver works on top of the TI_ST shared transport > > > > > line discipline driver which also allows other drivers like > > > > > FM V4L2 and GPS character driver to make use of the same UART > interface. > > > > > > > > > > Signed-off-by: Pavan Savoy > > > > > --- > > > > > drivers/bluetooth/bt_ti.c | 463 > ++++++++++++++++++++++++++++++++++++ > > > > > drivers/staging/ti-st/bt_drv.c | 509 --------------------------= ----- > --------- > > > > > drivers/staging/ti-st/bt_drv.h | 61 ----- > > > > > 3 files changed, 463 insertions(+), 570 deletions(-) > > > > > create mode 100644 drivers/bluetooth/bt_ti.c > > > > > delete mode 100644 drivers/staging/ti-st/bt_drv.c > > > > > delete mode 100644 drivers/staging/ti-st/bt_drv.h > > > > > > > > I don't care about staging at all. So you sort that out with Greg. > > > > > > > > Submit your driver for upstream inclusion. And once accepted you ca= n pin > > > > Greg about removing it. > > > > > > The driver is already in staging, this is the request to move it out = of > > > staging and into the "correct" place in the tree. The core of the ti= -st > > > code is now in the drivers/misc/ directory in the linux-next tree, an= d > > > this patch is the request to move the bluetooth drive into the proper > > > drivers/bluetooth/ location. > > > > nice idea, but I don't want it that way. I am not dealing with staging > > at all. They can submit this driver for upstream inclusion and then > > delete it in a second step from staging. Or the other way around. >=20 > We just have to be sure to do both steps in the same release cycle, > otherwise we could ship the driver twice in the kernel (considering we > will delete it after merge in drivers/bluetooth/) Yes, once this is reviewed, I will send across patches to delete it from st= aging. Also note, I have sent across updates patches, So please review. The shared transport design can be found @ http://omappedia.org/wiki/Wilink= _ST > Gustavo F. Padovan > ProFUSION embedded systems - http://profusion.mobi