public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: pavan_savoy@ti.com
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk, devel@driverdev.osuosl.org
Subject: Re: [PATCH 0/4] move TI_ST driver out of staging
Date: Tue, 5 Oct 2010 16:22:58 -0700	[thread overview]
Message-ID: <20101005232258.GA17277@kroah.com> (raw)
In-Reply-To: <1286323717-2925-1-git-send-email-pavan_savoy@ti.com>

On Tue, Oct 05, 2010 at 08:08:33PM -0400, pavan_savoy@ti.com wrote:
> From: Pavan Savoy <pavan_savoy@ti.com>
> 
> Texas Instrument's WiLink 7 chipset packs wireless technologies like
> Bluetooth, FM, GPS and WLAN into a single die.
> Among these the Bluetooth, FM Rx/Tx and GPS are interfaced to a apps processor
> over a single UART.
> 
> This line discipline driver allows various protocol drivers such as Bluetooth
> BlueZ driver, FM V4L2 driver and GPS simple character device driver
> to communicate with its relevant core in the chip.
> 
> The following patches,
> 1. removes the driver from staging
> 2. adds the driver to drivers/misc/ directory since it really doesn't
> belong anywhere else
> 3. adds in the Kconfig and Makefile for the driver
> 4. modifies the drivers/misc/Kconfig and drivers/misc/Makefile for the
> driver to be available to be built along with rest of the kernel.
> 
> Pavan Savoy (4):
>   drivers:staging:ti-st: remove TI_ST from staging
>   drivers:misc: ti-st: sources for TI_ST driver

These two should be together, so we see an obvious "move the files" type
patch, not a "delete and then add" set of stuff.

>   drivers:misc: ti-st: Kconfig & Makefile for TI_ST
>   drivers:misc: modify Kconfig & Makefile for TI_ST

So this really could just be one patch all at once, care to redo?

thanks,

greg k-h

  reply	other threads:[~2010-10-05 23:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06  0:08 [PATCH 0/4] move TI_ST driver out of staging pavan_savoy
2010-10-05 23:22 ` Greg KH [this message]
2010-10-05 23:47   ` Savoy, Pavan
2010-10-06  0:08 ` [PATCH 1/4] drivers:staging:ti-st: remove TI_ST from staging pavan_savoy
2010-10-06  0:08   ` [PATCH 2/4] drivers:misc: ti-st: sources for TI_ST driver pavan_savoy
2010-10-06  0:08     ` [PATCH 3/4] drivers:misc: ti-st: Kconfig & Makefile for TI_ST pavan_savoy
2010-10-06  0:08       ` [PATCH 4/4] drivers:misc: modify " pavan_savoy

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=20101005232258.GA17277@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