From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Len Brown <lenb@kernel.org>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
ibm-acpi-devel@lists.sourceforge.net, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 09/13] ACPI: thinkpad-acpi: handle HKEY thermal and battery alarms
Date: Thu, 15 Jan 2009 19:51:10 +0000 [thread overview]
Message-ID: <20090115195110.GA4200@srcf.ucam.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0901151342011.4737@localhost.localdomain>
On Thu, Jan 15, 2009 at 01:45:19PM -0500, Len Brown wrote:
> While useful to a techie, it is hard to imagine that these will
> become useful to a generic Linux GUI some day that is used by
> regular people.
I think it makes sense to tie them to uevents on the appropriate generic
devices. Even if most hardware doesn't generate them, the ability to pop
up a notification telling the user that the firmware thinks their system
is too hot is useful.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2009-01-15 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 5:01 [PATCH 09/13] ACPI: thinkpad-acpi: handle HKEY thermal and battery alarms Henrique de Moraes Holschuh
2009-01-15 18:45 ` Len Brown
2009-01-15 19:51 ` Matthew Garrett [this message]
2009-01-16 3:06 ` Henrique de Moraes Holschuh
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=20090115195110.GA4200@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox