All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [PATCH 1/4] strip: move driver to staging
Date: Tue, 20 Oct 2009 09:06:27 -0700	[thread overview]
Message-ID: <20091020090627.f36130fb.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1256015830-12700-1-git-send-email-linville@tuxdriver.com>

On Tue, 20 Oct 2009 14:17:07 +0900 John W. Linville wrote:

> Move the strip ("Starmode Radio IP") driver to drivers/staging.  For
> several years this driver has only seen API "bombing-run" changes, and
> few people ever had the hardware.  This driver represents unnecessary
> ongoing maintenance for no clear benefit.
> 
> This patch brought to you by the "hacking" session at the 2009 Kernel
> Summit in Tokyo, Japan...

is drivers/staging/ a temporary home or a permanent home?

so no explanation of what it means to be in drivers/staging/ and
no warning to users?  either in Kconfig or in feature-removal-schedule.txt?


> Signed-off-by: John W. Linville <linville@tuxdriver.com>
> ---
>  drivers/net/wireless/Kconfig   |   23 -
>  drivers/net/wireless/Makefile  |    1 -
>  drivers/net/wireless/strip.c   | 2805 ----------------------------------------
>  drivers/staging/Kconfig        |    2 +
>  drivers/staging/Makefile       |    1 +
>  drivers/staging/strip/Kconfig  |   22 +
>  drivers/staging/strip/Makefile |    1 +
>  drivers/staging/strip/strip.c  | 2805 ++++++++++++++++++++++++++++++++++++++++
>  8 files changed, 2831 insertions(+), 2829 deletions(-)
>  delete mode 100644 drivers/net/wireless/strip.c
>  create mode 100644 drivers/staging/strip/Kconfig
>  create mode 100644 drivers/staging/strip/Makefile
>  create mode 100644 drivers/staging/strip/strip.c


---
~Randy

  parent reply	other threads:[~2009-10-20 16:08 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20  5:17 [PATCH 1/4] strip: move driver to staging John W. Linville
2009-10-20  5:17 ` [PATCH 2/4] arlan: " John W. Linville
     [not found]   ` <1256015830-12700-3-git-send-email-linville@tuxdriver.com>
2009-10-20  5:17     ` [PATCH 4/4] netwave: " John W. Linville
2009-10-27 20:36       ` Staging: " Greg KH
2009-10-27 21:05         ` John W. Linville
2009-10-27 22:12           ` Greg KH
2009-10-20 16:06 ` Randy Dunlap [this message]
2009-10-26 16:46   ` [PATCH 1/4] strip: " John W. Linville
2009-10-26 17:02     ` Randy Dunlap
2009-10-26 18:48       ` Greg KH
2009-10-23 16:10 ` Pavel Machek
2009-10-23 16:54   ` Alan Cox
2009-10-26 16:55   ` John W. Linville
2009-10-26 17:18     ` david
2009-10-26 17:43       ` John W. Linville
2009-10-26 18:47       ` Greg KH
2009-10-27  4:17         ` david
2009-10-27  5:21           ` David Miller
2009-10-27  8:34           ` Stefan Richter
2009-10-27 14:08           ` Greg KH
2009-10-27 18:39             ` david
2009-10-27 20:38               ` Greg KH
2009-10-27 21:13               ` John W. Linville
2009-10-27 21:32               ` Alan Cox
2009-10-26 17:24     ` Pavel Machek
2009-10-26 17:29       ` Alan Cox
2009-10-26 17:34       ` John W. Linville
2009-10-26 18:48       ` Greg KH
2009-10-26 19:07         ` Joe Perches
2009-10-26 19:17           ` Greg KH
2009-10-26 19:20           ` John W. Linville
2009-10-26 19:36             ` Greg KH
2009-10-26 20:06             ` Joe Perches

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=20091020090627.f36130fb.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.