From: greg@kroah.com (Greg KH)
To: lm-sensors@vger.kernel.org
Subject: 2.4.22 kernel patches available
Date: Thu, 19 May 2005 06:24:15 +0000 [thread overview]
Message-ID: <20030903234952.GB1578@kroah.com> (raw)
In-Reply-To: <20030831172730.775fb950.khali@linux-fr.org>
On Sun, Aug 31, 2003 at 05:27:30PM +0200, Jean Delvare wrote:
>
> I noticed that new I2C drivers exist there: i2c-sibyte (plus
> i2c-algo-sibyte) and i2c-max1617. Why they end up there without us even
> hearing about it is a complete mystery to me. The max1617 driver is
> crappy (polling + working only with the sibyte bus) and completely
> useless since we already support that chip for years. The bus driver
> probably should have been built into a single module. And none of these
> modules will even compile since they use I2C IDs that are not defined.
>
> My 2.4.22 patch simply wipe them out. I can't understand how they were
> accepted into the main kernel tree. I couldn't find anything related to
> them in the kernel changelog nor in LKML archives.
These all came in from the merge with the MIPS maintainer. Bitkeeper is
nice :)
> I feel like we should complain about that, but unfortunately I don't
> have time for that right now. Greg, you have more contact with the
> kernel people than any of us here, do you have any information we
> don't have?
Why complain? What is it hurting? The cvs code sure isn't in the
kernel tree so what do we have to base our complaint on? :)
So I'm guessing that some people with MIPS platforms actually use this
driver. Good for them. I would not recommend that your patches "wipe
them out" for that reason.
thanks,
greg k-h
next prev parent reply other threads:[~2005-05-19 6:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 6:24 2.4.22 kernel patches available Jean Delvare
2005-05-19 6:24 ` Mark D. Studebaker
2005-05-19 6:24 ` Greg KH [this message]
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Greg KH
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Jean Delvare
2005-05-19 6:24 ` Greg KH
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=20030903234952.GB1578@kroah.com \
--to=greg@kroah.com \
--cc=lm-sensors@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.