From: Jean Delvare <khali@linux-fr.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
linux-acpi@vger.kernel.org, Len Brown <lenb@kernel.org>,
LM Sensors <lm-sensors@lm-sensors.org>
Subject: Re: [lm-sensors] [PATCH] hwmon: (asus_atk0110) Don't load if ACPI resources aren't enforced
Date: Wed, 31 Mar 2010 15:37:19 +0200 [thread overview]
Message-ID: <20100331153719.5c700763@hyperion.delvare> (raw)
In-Reply-To: <20100331132711.GA17104@srcf.ucam.org>
On Wed, 31 Mar 2010 14:27:11 +0100, Matthew Garrett wrote:
> If the firmware tells us that a resource range using indexed access is
> reserved, it's not safe to assume that the firmware isn't using it.
Whether it is safe of not is irrelevant. The user is telling us he/she
_will_ use it nevertheless. So what is wrong with doing our best to
avoid problems?
The user paid for the hardware, and firmwares are often crappy. You
know that better than anyone else, having worked on ACPI for some time
now.
--
Jean Delvare
next prev parent reply other threads:[~2010-03-31 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100309135636.373a40a9@hyperion.delvare>
2010-03-30 10:03 ` [lm-sensors] [PATCH] hwmon: (asus_atk0110) Don't load if ACPI resources aren't enforced Jean Delvare
2010-03-30 13:21 ` Matthew Garrett
2010-03-30 19:47 ` Jean Delvare
2010-03-30 19:48 ` Matthew Garrett
2010-03-30 20:32 ` Jean Delvare
2010-03-30 21:10 ` Matthew Garrett
2010-03-30 21:45 ` [lm-sensors] " Luca Tettamanti
2010-03-30 21:53 ` Matthew Garrett
2010-03-31 7:30 ` Jean Delvare
2010-03-31 12:51 ` Matthew Garrett
2010-03-31 13:25 ` Jean Delvare
2010-03-31 13:27 ` Matthew Garrett
2010-03-31 13:37 ` Jean Delvare [this message]
2010-03-31 7:42 ` Jean Delvare
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=20100331153719.5c700763@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=kronos.it@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=mjg59@srcf.ucam.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