From: Greg KH <greg@kroah.com>
To: "Savoy, Pavan" <pavan_savoy@ti.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] prepare TI_ST to move out of staging
Date: Tue, 5 Oct 2010 13:06:49 -0700 [thread overview]
Message-ID: <20101005200649.GA4228@kroah.com> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739404AA21CB20@dbde02.ent.ti.com>
On Wed, Oct 06, 2010 at 12:27:46AM +0530, Savoy, Pavan wrote:
> > So, on to moving the drivers out of the staging tree, right? Care to
> > send me patches for them? Have you gotten the bluetooth driver reviewed
> > yet?
>
> No not yet.
> I had planned to put up a patch to move the st_core.c, st_kim.c and
> st_ll.c to drivers/misc/ first.
That is fine.
> Then put together Bluetooth header and driver where in I will bring in
> Marcel/Johan & linux-bluetooth into the loop. Then move the unified
> bt_drv.c to something like ti_st_bt.c to drivers/bluetooth/
>
> Does this sound OK?
Yes it does. Feel free to send patches for the first part above on if
you want to.
thanks,
greg k-h
next prev parent reply other threads:[~2010-10-05 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 20:13 [PATCH 0/3] prepare TI_ST to move out of staging pavan_savoy
2010-09-30 20:13 ` [PATCH 1/3] include:linux: tty.h: new ldisc for TI WiLink ST pavan_savoy
2010-09-30 20:13 ` [PATCH 2/3] drivers:staging:ti-st: drop the __KERNEL__ pavan_savoy
2010-09-30 20:13 ` [PATCH 3/3] drivers:staging:ti-st: mv ti_wilink_st header pavan_savoy
2010-10-05 18:23 ` [PATCH 0/3] prepare TI_ST to move out of staging Savoy, Pavan
2010-10-05 18:49 ` Greg KH
2010-10-05 18:57 ` Savoy, Pavan
2010-10-05 20:06 ` Greg KH [this message]
2010-10-05 19:10 ` Savoy, Pavan
2010-10-05 20:07 ` Greg KH
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=20101005200649.GA4228@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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