From: Jean Delvare <khali@linux-fr.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: i2c@lm-sensors.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] the scheduled i2c-rpx removal
Date: Thu, 12 Jul 2007 13:51:39 +0200 [thread overview]
Message-ID: <20070712135139.317978c1@hyperion.delvare> (raw)
In-Reply-To: <20070711180348.02dfd257@hyperion.delvare>
Hi again Adrian,
On Wed, 11 Jul 2007 18:03:48 +0200, Jean Delvare wrote:
> On Mon, 9 Jul 2007 16:57:24 +0200, Adrian Bunk wrote:
> > This patch contains the scheduled removal of the i2c-rpx driver.
> >
> > Signed-off-by: Adrian Bunk <bunk@stusta.de>
> >
> > ---
> >
> > Documentation/feature-removal-schedule.txt | 8 -
> > Documentation/i2c/summary | 1
> > drivers/i2c/algos/Kconfig | 4
> > drivers/i2c/busses/Kconfig | 5 -
> > drivers/i2c/busses/Makefile | 1
> > drivers/i2c/busses/i2c-rpx.c | 101 ---------------------
> > 6 files changed, 120 deletions(-)
>
> I already have a patch doing this in my tree.
>
> Also note that the entry in feature-removal-schedule.txt never made it
> to mainline (it was in -mm only), so it can't be removed.
>
> In theory there is a driver rewrite in progress, so my plan is to
> include this removal patch into -mm for now, and send it to Linus only
> for 2.6.24 if I don't receive an acceptable driver meanwhile.
I've changed my mind. The new driver will be so much bigger and
different from the current i2c-rpx driver that there's hardly any
benefit in keeping the old driver around. So I'll push this cleanup
patch to Linus for 2.6.23.
--
Jean Delvare
prev parent reply other threads:[~2007-07-12 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:57 Adrian Bunk
2007-07-11 16:03 ` Jean Delvare
2007-07-12 11:51 ` Jean Delvare [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=20070712135139.317978c1@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=bunk@stusta.de \
--cc=i2c@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®