All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Andres Salomon <dilinger@queued.net>
Cc: Daniel Drake <dsd@laptop.org>,
	linux-kernel@vger.kernel.org, linux-geode@lists.infradead.org,
	Ben Gardner <bgardner@wabtec.com>, Greg KH <greg@kroah.com>
Subject: Re: [PATCH] cs5535: deprecate older cs5535_gpio driver
Date: Thu, 9 Dec 2010 13:13:37 -0800	[thread overview]
Message-ID: <20101209131337.be92caf6.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101209125737.065e91fd@queued.net>

On Thu, 9 Dec 2010 12:57:37 -0800
Andres Salomon <dilinger@queued.net> wrote:

> The newer drivers/gpio/cs5535-gpio.c replaces
> drivers/misc/cs5535_gpio.c.  The new driver has been in the tree
> for a little while, and has received some testing; it's time to mark
> the old one as deprecated.  I'm thinking removal around 2.6.40 would
> be good, provided we're not missing critical functionality in the
> newer driver.
> 
> Signed-off-by: Andres Salomon <dilinger@queued.net>
> ---
>  Documentation/feature-removal-schedule.txt |   14 ++
>  drivers/char/Kconfig                       |    9 -
>  drivers/char/Makefile                      |    1 -
>  drivers/char/cs5535_gpio.c                 |  259 ----------------------------
>  drivers/staging/Kconfig                    |    2 +
>  drivers/staging/Makefile                   |    1 +
>  drivers/staging/cs5535_gpio/Kconfig        |   11 ++
>  drivers/staging/cs5535_gpio/Makefile       |    1 +
>  drivers/staging/cs5535_gpio/TODO           |    6 +
>  drivers/staging/cs5535_gpio/cs5535_gpio.c  |  259 ++++++++++++++++++++++++++++
>  10 files changed, 294 insertions(+), 269 deletions(-)
>  delete mode 100644 drivers/char/cs5535_gpio.c
>  create mode 100644 drivers/staging/cs5535_gpio/Kconfig
>  create mode 100644 drivers/staging/cs5535_gpio/Makefile
>  create mode 100644 drivers/staging/cs5535_gpio/TODO
>  create mode 100644 drivers/staging/cs5535_gpio/cs5535_gpio.c

It seems logical (although not particularly useful) to use
drivers/staging/ as the site for unstaging things as well, but is that
something which we normally do?


  reply	other threads:[~2010-12-09 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 20:57 [PATCH] cs5535: deprecate older cs5535_gpio driver Andres Salomon
2010-12-09 21:13 ` Andrew Morton [this message]
2010-12-09 21:23   ` Andres Salomon
2010-12-09 21:28   ` Greg KH
2010-12-10 15:09 ` BGardner

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=20101209131337.be92caf6.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bgardner@wabtec.com \
    --cc=dilinger@queued.net \
    --cc=dsd@laptop.org \
    --cc=greg@kroah.com \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.