Re: [PATCH] cs5535: deprecate older cs5535_gpio driver

[Andres Salomon]

On Thu, 9 Dec 2010 13:13:37 -0800
Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Thu, 9 Dec 2010 12:57:37 -0800
> Andres Salomon <dilinger@xxxxxxxxxx> 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@xxxxxxxxxx>
> > ---
> >  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?
> 

FYI, I was using commits 7af97eff and 96322b80 as an example... Though
I suppose I really should've chosen commits by two separate authors
(oops).

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/