From: mds@paradyne.com (Mark D. Studebaker )
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: <3F523D32.7080304@paradyne.com> (raw)
In-Reply-To: <20030831172730.775fb950.khali@linux-fr.org>
On sybyte and max1617 we should try and find the authors and bring them into the fold.
On you moving on, hopefully you can find 1-2 hours a week for us which would
still qualify you as "active"! We've appreciated your energy and enthusiasm
(and new ideas) over the recent months, especially as it came when
I was running out of all of those...
Any proposal for how to proceed with the 2.4 patch?
Without you to generate a 2.8.1->2.4.23 patch, what should we do?
And if you don't mind, what are you going to be doing for a living?
thanks again
mds
Jean Delvare wrote:
> Hi all,
>
> I just finished updating my installation guide to support the new 2.4.22
> kernel.
>
> 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. 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?
>
> I am taking a new (well...) job tomorrow. At last :) I'm more than
> pleased, but you have to understand that this also means the end of my
> active participation to the LM Sensors project. Don't worry, I won't
> leave the project completely and within a few months I hope I'll have
> some time left again to contribute. But I won't spend 6 hours a day on
> it as it has been the case for the last few months. BTW, I'd like to
> thank you all very much for that. I've learned much here, and it also
> prevented me from falling into the laziness :)
>
> See you later.
>
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 ` Greg KH
2005-05-19 6:24 ` Mark D. Studebaker [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=3F523D32.7080304@paradyne.com \
--to=mds@paradyne.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.