From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Adrian Bunk <bunk@kernel.org>,
i2c@lm-sensors.org, Lennert Buytenhek <buytenh@wantstofly.org>,
linux-kernel@vger.kernel.org
Subject: Re: [i2c] [2.6 patch] some overdue I2C driver removal
Date: Wed, 28 Nov 2007 14:04:09 -0500 [thread overview]
Message-ID: <20071128190409.GE2308@csclub.uwaterloo.ca> (raw)
In-Reply-To: <9e4733910711280943t75564912m805cfdb2fe099528@mail.gmail.com>
On Wed, Nov 28, 2007 at 12:43:00PM -0500, Jon Smirl wrote:
> Hasn't their been a one year notice that these drivers were going to
> be removed? How about removing them and putting them into a tarball on
> the i2c web site with a note explaining about how they need to be
> updated to use the gpio driver? Then if someone really wants to use
> the old drivers they can use them out of tree.
Why remove a working driver? Who gets to decide that everyone must go
use this gpio api based system that isn't yet supported by all
platforms? If someone thinks the old drivers should be replaced by new
ones using the new GPIO API then they should go implement it, and then
when it works they can remove the old one. You can't just declare that
you think the old one sucks and should be removed and if anyone else
cares they should go make a working driver to replace it.
--
Len Sorensen
next prev parent reply other threads:[~2007-11-28 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:25 Adrian Bunk
2007-10-24 16:43 ` Lennart Sorensen
2007-11-28 10:23 ` Jean Delvare
2007-11-28 17:30 ` Lennart Sorensen
2007-11-28 17:43 ` [i2c] " Jon Smirl
2007-11-28 17:53 ` Jean Delvare
2007-11-28 17:54 ` Russell King
2007-11-28 19:04 ` Lennart Sorensen [this message]
2007-11-28 17:41 ` Russell King
2007-11-28 18:37 ` Lennert Buytenhek
2007-11-28 19:07 ` Jean Delvare
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=20071128190409.GE2308@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=bunk@kernel.org \
--cc=buytenh@wantstofly.org \
--cc=i2c@lm-sensors.org \
--cc=jonsmirl@gmail.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
/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®