From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [RFC-patch] pc87360 - unchecked
Date: Fri, 18 Aug 2006 11:48:28 +0000 [thread overview]
Message-ID: <20060818134828.c1188dc1.khali@linux-fr.org> (raw)
In-Reply-To: <44D2514B.2090202@gmail.com>
Jim,
> BTW - are you considering these as 18 bugfix material, or are they
> "long standing sub-optimalities" for 19 when it opens ? (ie when 18 is out)
>
> Obviously (from the experimentalism in my patches), Ive been treating it
> as 19 stuff ;-)
Definitely not .18, as they don't fix any bug. So it's .19 material,
for what we can have ready before the .19 merge window. All drivers
need to be converted, this is a significant amount of work. Also the
change is likely to break other patches, so I don't want to wait for
all drivers to be converted to push all the patches - this would block
too many other patches. We can make several batches, one for .19 and
one or more after that.
A summary would be: ".19 at earliest, then as soon as possible, as time
permits". This is a background job, we have many other, more important
things in the works.
> Apologies for making this more *in-need-of-feedback* than it has to be,
> but I guess I cant quite resist..
No worry, getting feedback is the point of posting to a mailing list :)
--
Jean Delvare
next prev parent reply other threads:[~2006-08-18 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 19:40 [lm-sensors] [RFC-patch] pc87360 - unchecked Jim Cromie
2006-08-13 19:45 ` Mark M. Hoffman
2006-08-14 13:17 ` Jean Delvare
2006-08-16 5:35 ` Jim Cromie
2006-08-16 21:04 ` Jean Delvare
2006-08-17 19:35 ` Jim Cromie
2006-08-17 20:01 ` Greg KH
2006-08-17 21:45 ` Jim Cromie
2006-08-18 2:45 ` Mark M. Hoffman
2006-08-18 4:35 ` Greg KH
2006-08-18 11:48 ` Jean Delvare [this message]
2006-08-18 21:21 ` 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=20060818134828.c1188dc1.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.