From: "Gustavo F. Padovan" <padovan@profusion.mobi>
To: Greg KH <greg@kroah.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
pavan-savoy@ti.com, linux-bluetooth@vger.kernel.org,
johan.hedberg@gmail.com, linux-kernel@vger.kernel.org,
Pavan Savoy <pavan_savoy@ti.com>
Subject: Re: [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver
Date: Thu, 7 Oct 2010 14:51:48 -0300 [thread overview]
Message-ID: <20101007175148.GC4893@vigoh> (raw)
In-Reply-To: <20101007143409.GB14913@kroah.com>
Hi Greg,
* Greg KH <greg@kroah.com> [2010-10-07 07:34:09 -0700]:
> On Thu, Oct 07, 2010 at 12:05:48PM +0200, Marcel Holtmann wrote:
> > Hi Pavan,
> >
> > > 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 <pavan_savoy@ti.com>
> > > ---
> > > 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 can 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, and
> this patch is the request to move the bluetooth drive into the proper
> drivers/bluetooth/ location.
I'm wondering why this driver never touched linux-bluetooth before. It
is on staging because it is not ready for a proper merge and while it is
not ready it needs the comments from the bluetooth developers here to
get it ready for merge in drivers/bluetooth. So why this never arrived
here before?
--
Gustavo F. Padovan
ProFUSION embedded systems - http://profusion.mobi
next prev parent reply other threads:[~2010-10-07 17:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 22:34 [PATCH 0/2] Bluetooth driver for TI WiLink 7 pavan-savoy
2010-10-06 22:34 ` [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver pavan-savoy
2010-10-06 22:34 ` [PATCH 2/2] drivers:bluetooth: Kconfig & Makefile for TI BT pavan-savoy
2010-10-07 10:05 ` [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver Marcel Holtmann
2010-10-07 14:34 ` Greg KH
2010-10-07 15:21 ` Marcel Holtmann
2010-10-07 15:35 ` Greg KH
2010-10-07 17:57 ` Gustavo F. Padovan
2010-10-07 21:24 ` Savoy, Pavan
2010-10-07 17:51 ` Gustavo F. Padovan [this message]
2010-10-07 21:30 ` Greg KH
2010-10-07 19:09 ` Gustavo F. Padovan
2010-10-07 22:17 ` Greg KH
2010-10-07 19:44 ` Gustavo F. Padovan
2010-10-07 14:59 ` Savoy, Pavan
2010-10-07 15:17 ` Marcel Holtmann
2010-10-07 15:23 ` Savoy, Pavan
2010-10-07 15:37 ` Marcel Holtmann
2010-10-07 15:47 ` Savoy, Pavan
2010-10-07 15:49 ` Marcel Holtmann
2010-10-07 15:52 ` Savoy, Pavan
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 18:47 [PATCH 0/2] v2: Bluetooth driver for TI_ST pavan_savoy
2010-10-07 18:47 ` [PATCH 1/2] drivers:bluetooth: TI_ST bluetooth driver pavan_savoy
2010-10-07 18:45 ` Gustavo F. Padovan
2010-10-07 21:53 ` Savoy, Pavan
2010-10-08 8:37 ` Marcel Holtmann
2010-10-08 14:54 ` Savoy, Pavan
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=20101007175148.GC4893@vigoh \
--to=padovan@profusion.mobi \
--cc=greg@kroah.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavan-savoy@ti.com \
--cc=pavan_savoy@ti.com \
/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).