mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: "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>,
	Jean Delvare <khali@linux-fr.org>,
	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: Mon, 23 Jun 2008 20:07:15 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806232004480.2926@woody.linux-foundation.org> (raw)
In-Reply-To: <48605935.5070407@shaw.ca>



On Mon, 23 Jun 2008, Robert Hancock wrote:

> Mark M. Hoffman wrote:
> > 
> > 1) The bug is in libsensors (2.10), not the kernel.
> 
> This doesn't matter. Breaking userspace in such a fashion is severely frowned
> upon unless essentially unavoidable, even if it is just triggering a bug.

I do tend to agree. If it used to work, it should continue to work, even 
if it wasn't _meant_ to work.

That's not always 100% possible, but the fact is, neither is updating user 
space always possible. The kernel needs to try its best to maintain stable 
interfaces, and no, "..but the interface was broken" is _not_ an 
acceptable excuse for unbreaking it if it causes problems.

> > - but more importantly -
> > 
> > 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.

		Linus

  reply	other threads:[~2008-06-24  3:08 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   ` Robert Hancock
2008-06-24  3:07     ` Linus Torvalds [this message]
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
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=alpine.LFD.1.10.0806232004480.2926@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=hancockr@shaw.ca \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=khali@linux-fr.org \
    --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 \
    /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

Powered by JetHome