From: Stefan Seyfried <seife@suse.de>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <linux-acpi@vger.kernel.org>
Subject: Re: acpiphp makes noise on every lid close/open
Date: Mon, 6 Nov 2006 09:19:27 +0100 [thread overview]
Message-ID: <20061106081927.GA9063@suse.de> (raw)
In-Reply-To: <20061105232944.GA23256@vasa.acc.umu.se>
On Mon, Nov 06, 2006 at 12:29:44AM +0100, David Weinehall wrote:
> On Thu, Nov 02, 2006 at 05:54:03PM -0800, Kristen Carlson Accardi wrote:
>
> > There is a bug here in that acpiphp shouldn't even be used on the X60 -
> > it has no hotpluggable slots.
>
> How about the docking station?
Hm, i haven't seen one - i only saw the "media slice" (or however it is
called this week) which gives you a drive bay, but no additional PCI
devices, so it does not count.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Seyfried <seife@suse.de>
To: Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
ACPI mailing list <linux-acpi@vger.kernel.org>
Subject: Re: acpiphp makes noise on every lid close/open
Date: Mon, 6 Nov 2006 09:19:27 +0100 [thread overview]
Message-ID: <20061106081927.GA9063@suse.de> (raw)
In-Reply-To: <20061105232944.GA23256@vasa.acc.umu.se>
On Mon, Nov 06, 2006 at 12:29:44AM +0100, David Weinehall wrote:
> On Thu, Nov 02, 2006 at 05:54:03PM -0800, Kristen Carlson Accardi wrote:
>
> > There is a bug here in that acpiphp shouldn't even be used on the X60 -
> > it has no hotpluggable slots.
>
> How about the docking station?
Hm, i haven't seen one - i only saw the "media slice" (or however it is
called this week) which gives you a drive bay, but no additional PCI
devices, so it does not count.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
next prev parent reply other threads:[~2006-11-06 8:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 11:56 acpiphp makes noise on every lid close/open Pavel Machek
2006-11-03 1:54 ` Kristen Carlson Accardi
2006-11-05 23:29 ` David Weinehall
2006-11-06 8:19 ` Stefan Seyfried [this message]
2006-11-06 8:19 ` Stefan Seyfried
2006-11-06 9:21 ` Pavel Machek
2006-11-06 13:29 ` Henrique de Moraes Holschuh
2006-11-06 17:32 ` Tomasz Torcz
2006-11-06 19:13 ` Stefan Seyfried
2006-11-06 19:13 ` Stefan Seyfried
2006-11-06 19:47 ` Henrique de Moraes Holschuh
2006-11-07 20:44 ` David Weinehall
2006-11-07 21:44 ` Kristen Carlson Accardi
2006-11-17 10:22 ` David Weinehall
2006-11-17 15:13 ` Matthew Garrett
2006-11-17 15:15 ` Pavel Machek
2006-11-17 15:37 ` David Weinehall
2006-11-17 15:46 ` Matthew Garrett
2006-11-17 16:08 ` David Weinehall
2006-11-17 16:31 ` Matthew Garrett
2006-11-17 18:18 ` David Weinehall
2006-11-17 18:35 ` Matthew Garrett
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=20061106081927.GA9063@suse.de \
--to=seife@suse.de \
--cc=kristen.c.accardi@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.