From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: ACPI mailing list
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Andrew Grover
<andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: kacpidpc needs to die
Date: Tue, 7 Jan 2003 19:51:36 +0100 [thread overview]
Message-ID: <20030107185136.GA302@elf.ucw.cz> (raw)
Hi!
For reasons discussed before [forking from timer is not safe, anyway],
kacpidpc needs to die. Andrew, are you going to kill it or should I do
it?
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: ACPI mailing list <acpi-devel@lists.sourceforge.net>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Grover <andrew.grover@intel.com>
Subject: kacpidpc needs to die
Date: Tue, 7 Jan 2003 19:51:36 +0100 [thread overview]
Message-ID: <20030107185136.GA302@elf.ucw.cz> (raw)
Hi!
For reasons discussed before [forking from timer is not safe, anyway],
kacpidpc needs to die. Andrew, are you going to kill it or should I do
it?
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next reply other threads:[~2003-01-07 18:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 18:51 Pavel Machek [this message]
2003-01-07 18:51 ` kacpidpc needs to die Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-01-08 18:57 Grover, Andrew
2003-01-08 18:57 ` Grover, Andrew
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=20030107185136.GA302@elf.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.