From: David Brownell <david-b@pacbell.net>
To: eric miao <eric.y.miao@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
linux-kernel@vger.kernel.org, i2c@lm-sensors.org,
bgardner@wabtec.com
Subject: Re: [PATCH 2.6.24-rc5-mm 3/3] gpiolib: obsolete drivers/i2c/chips/pca9539.c
Date: Sun, 23 Dec 2007 10:32:02 -0800 [thread overview]
Message-ID: <200712231032.02438.david-b@pacbell.net> (raw)
In-Reply-To: <f17812d70712190132j31d22070rae986f2ed31d3634@mail.gmail.com>
> From: eric miao <eric.miao@marvell.com>
> Date: Wed, 19 Dec 2007 16:40:04 +0800
> Subject: [PATCH] gpiolib: mark drivers/i2c/chips/pca9539.c as deprecated
>
> use drivers/gpio/pca9539.c instead.
>
> Signed-off-by: eric miao <eric.miao@marvell.com>
> Acked-by: Ben Gardner <bgardner@wabtec.com>
> Acked-by: Jean Delvare <khali@linux-fr.org>
> ---
> Documentation/i2c/chips/pca9539 | 3 +++
> drivers/i2c/chips/Kconfig | 7 +++++--
> 2 files changed, 8 insertions(+), 2 deletions(-)
Yeah, this version looks unlikely to break anyone's systems.
> @@ -75,6 +75,9 @@ config SENSORS_PCA9539
> This driver can also be built as a module. If so, the module
> will be called pca9539.
>
> + This driver is deprecated and will be dropped soon. Use
> + drivers/gpio/pca9539.c instead.
> +
> config SENSORS_PCF8591
> tristate "Philips PCF8591"
> depends on EXPERIMENTAL
>
I suggest defining a date, such as "will be removed in the 2.6.26
kernel", and adding it to Documentation/feature-removal-schedule.txt ...
prev parent reply other threads:[~2007-12-23 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 4:16 [PATCH 2.6.24-rc5-mm 3/3] gpiolib: obsolete drivers/i2c/chips/pca9539.c eric miao
2007-12-16 19:42 ` Jean Delvare
2007-12-17 6:33 ` eric miao
2007-12-17 18:09 ` David Brownell
2007-12-17 20:29 ` Jean Delvare
2007-12-18 1:54 ` eric miao
2007-12-18 14:40 ` Jean Delvare
2007-12-19 8:45 ` eric miao
2007-12-19 9:01 ` Jean Delvare
2007-12-19 9:32 ` eric miao
2007-12-23 18:32 ` David Brownell [this message]
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=200712231032.02438.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=bgardner@wabtec.com \
--cc=eric.y.miao@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.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.