From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: linux-acpi@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
"Mark M. Hoffman" <mhoffman@lightlink.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
lm-sensors@lm-sensors.org
Subject: Re: [lm-sensors] [REGRESSION, ABI] Re: LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors
Date: Sun, 22 Jun 2008 20:07:41 +0200 [thread overview]
Message-ID: <485E94ED.10602@hhs.nl> (raw)
In-Reply-To: <485E6F12.4010307@keyaccess.nl>
Rene Herman wrote:
> On 22-06-08 16:29, Hans de Goede wrote:
>
>> Rene Herman wrote:
>>> This is an ABI breakage issue and an unfortunate one at that:
>>>
>>
>> No it is not, in 2.6.26rcX, the acpi thermalzones have grown a hwmon
>> interface, that is they register a hwmon device so that "sensors" and
>
> [ ... ]
>
> Now what? Yes it is. 2.6.25.7 works and 2.6.26-rcX with the same config
> options and the same userspace does not.
Know what? No it isn't. Just because some random userspace apps breaks because
certain _assumptions_ no longer hold true, does not make something an ABI breakage.
I agree with you that the results are still no good though.
Know something else? I've just stopped caring about this issue, I'm not the
author of the changes causing said breakage. I'm merely an lm_sensors (both
userspace and kernel space) developer who was heavily involved in getting this
fixed for lm_sensors-3.0.2, and I believe that adding yet another kconfig
option which we then carry for years and years is _not_ a good solution. Some
userspace utlities like udev sit very close to the kernel and sometimes an
kernel update mandates a new udev. To me this is much the same.
But at the end of the day, I do not feel responsible for this as I'm not the
author of the code causing the breakage. I'm just someone who knows the ins and
outs and tried to help, but given the treatment and thanks I've been getting
for my help I'm stopping with helping now.
Regards,
Hans
next prev parent reply other threads:[~2008-06-22 18:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 0:47 LMSENSORS: 2.6.26-rc, enabling ACPI Termal Zone support costs sensors Rene Herman
2008-06-22 7:28 ` [lm-sensors] " Hans de Goede
2008-06-22 13:15 ` [REGRESSION, ABI] " Rene Herman
2008-06-22 13:23 ` Rene Herman
2008-06-22 14:29 ` [lm-sensors] [REGRESSION, ABI] " Hans de Goede
2008-06-22 15:26 ` Rene Herman
2008-06-22 18:07 ` Hans de Goede [this message]
2008-06-22 18:25 ` Rene Herman
2008-06-22 21:58 ` Rene Herman
2008-06-23 1:44 ` Zhang Rui
2008-06-23 5:21 ` Hans de Goede
2008-06-23 10:40 ` Rene Herman
2008-06-23 11:06 ` Jean Delvare
2008-06-23 10:56 ` Jean Delvare
2008-06-23 17:54 ` [lm-sensors] [REGRESSION, ABI] " Len Brown
2008-06-23 19:54 ` Jean Delvare
2008-06-23 20:07 ` [lm-sensors] [REGRESSION, ABI] " Rene Herman
2008-06-23 20:24 ` Rene Herman
2008-06-22 15:43 ` Rene Herman
2008-06-23 10:08 ` Jean Delvare
2008-06-23 10:24 ` Rene Herman
2008-06-23 11:57 ` Jean Delvare
2008-06-23 12:35 ` Rene Herman
2008-06-23 13:47 ` Jean Delvare
2008-06-23 14:06 ` Rene Herman
2008-06-23 14:31 ` Matthew Garrett
2008-06-23 17:10 ` Rene Herman
2008-06-23 13:51 ` Hans de Goede
2008-06-22 7:30 ` [lm-sensors] " Hans de Goede
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=485E94ED.10602@hhs.nl \
--to=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 \
/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