From: Jean Delvare <khali@linux-fr.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Rene Herman <rene.herman@keyaccess.nl>,
Hans de Goede <j.w.r.degoede@hhs.nl>,
Zhang Rui <rui.zhang@intel.com>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.26-rc] ACPI Thermal Zone driver breaks lm-sensors 2 userspace
Date: Tue, 24 Jun 2008 08:59:40 +0200 [thread overview]
Message-ID: <20080624085940.3ee3bf77@hyperion.delvare> (raw)
In-Reply-To: <alpine.LFD.1.10.0806232004480.2926@woody.linux-foundation.org>
Hi Linus,
On Mon, 23 Jun 2008 20:07:15 -0700 (PDT), Linus Torvalds wrote:
> On Mon, 23 Jun 2008, Robert Hancock wrote:
> > Mark M. Hoffman wrote:
> > > 2) This patch is broken.
> >
> > You didn't indicate what was wrong with the patch.
>
> Yes. Leaving everybody wondering whether it's just an opinionated
> expression of the former problem, or whether there is a real and
> understandable reason why it was NACK'ed.
I guess Mark assumed that everybody had read the discussion thread Rene
referenced, where I explained why his patch was broken:
http://lkml.org/lkml/2008/6/23/175
--
Jean Delvare
next prev parent reply other threads:[~2008-06-24 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.4PGqX9CuLbgiTimfCcon+PlAMxk@ifi.uio.no>
[not found] ` <fa.PWu620xEt5OlYdOezvRtQriuNjM@ifi.uio.no>
2008-06-24 2:17 ` [PATCH 2.6.26-rc] ACPI Thermal Zone driver breaks lm-sensors 2 userspace Robert Hancock
2008-06-24 3:07 ` Linus Torvalds
2008-06-24 3:47 ` Zhang Rui
2008-06-24 12:14 ` Mark M. Hoffman
2008-06-24 17:38 ` Rene Herman
2008-06-25 23:12 ` Len Brown
2008-06-26 0:17 ` Matthew Garrett
2008-06-25 23:16 ` Len Brown
2008-06-25 23:38 ` Rene Herman
2008-06-26 0:57 ` Zhang Rui
2008-06-24 6:59 ` Jean Delvare [this message]
2008-06-24 9:28 ` Rene Herman
2008-06-24 11:45 ` Mark M. Hoffman
2008-06-23 15:06 Rene Herman
2008-06-23 17:06 ` Mark M. Hoffman
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=20080624085940.3ee3bf77@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=hancockr@shaw.ca \
--cc=j.w.r.degoede@hhs.nl \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mhoffman@lightlink.com \
--cc=rene.herman@keyaccess.nl \
--cc=rui.zhang@intel.com \
--cc=torvalds@linux-foundation.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