From: "Stefan Dösinger" <stefandoesinger@gmx.at>
To: acpi-devel@lists.sourceforge.net
Cc: Len Brown <len.brown@intel.com>, Pavel Machek <pavel@suse.cz>,
trenn@suse.de, seife@suse.de,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ACPI] Re: Allow userspace do something special on overtemp
Date: Thu, 12 Aug 2004 19:27:10 +0200 [thread overview]
Message-ID: <200408121927.11277.stefandoesinger@gmx.at> (raw)
In-Reply-To: <1092323945.5028.177.camel@dhcppc4>
Hi,
Isn't this a little bit dangerous? What if acpid is not set up to handle this?
next prev parent reply other threads:[~2004-08-12 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040811085326.GA11765@elf.ucw.cz>
2004-08-12 15:19 ` Allow userspace do something special on overtemp Len Brown
2004-08-12 15:16 ` Randy.Dunlap
2004-08-12 15:50 ` Stefan Seyfried
2004-08-12 17:27 ` Stefan Dösinger [this message]
[not found] ` <200408121927.11277.stefandoesinger-RbZlAiThDcE@public.gmane.org>
2004-08-12 22:53 ` Len Brown
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=200408121927.11277.stefandoesinger@gmx.at \
--to=stefandoesinger@gmx.at \
--cc=acpi-devel@lists.sourceforge.net \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=seife@suse.de \
--cc=trenn@suse.de \
/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