From: Robert Hancock <hancockr@shaw.ca>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Len Brown <lenb@kernel.org>,
"Brown, John M (WGBU R&D)" <john.brown3@hp.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ACPI suspend: Blacklist HP xw4600 Workstation for old code ordering
Date: Thu, 16 Oct 2008 22:07:11 -0600 [thread overview]
Message-ID: <48F80F6F.6090608@shaw.ca> (raw)
In-Reply-To: <fa.MkpTJy5Iw9ZR3PXWpugQeK5oN1o@ifi.uio.no>
Rafael J. Wysocki wrote:
> On Wednesday, 15 of October 2008, Len Brown wrote:
>> Matthew,
>> You are right, of course, we're not doing something right
>> if a new machine needs this workaround.
>
> Isn't that possible, however, that the BIOS of this new machine is based on an
> older one that used to have this problem?
Maybe, but it doesn't matter. If it's a new machine it's presumably
going to work fine on Vista, etc. so it doesn't make much sense that
this machine should require the old ACPI code ordering.
next parent reply other threads:[~2008-10-17 4:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa./6DR3VeG3JltQZvwctIdnZpBOO8@ifi.uio.no>
[not found] ` <fa.TMVI/3KJQDTBIWAfYmLw01GczF4@ifi.uio.no>
[not found] ` <fa./GCX/x0zwCB6BIEvtQehNpVDSVk@ifi.uio.no>
[not found] ` <fa.MkpTJy5Iw9ZR3PXWpugQeK5oN1o@ifi.uio.no>
2008-10-17 4:07 ` Robert Hancock [this message]
2008-10-14 20:54 [PATCH] ACPI suspend: Blacklist HP xw4600 Workstation for old code ordering Rafael J. Wysocki
2008-10-15 8:58 ` Matthew Garrett
2008-10-15 14:05 ` Rafael J. Wysocki
2008-10-15 14:15 ` Matthew Garrett
2008-10-15 20:35 ` Brown, John M (WGBU R&D)
2008-10-15 21:49 ` Len Brown
2008-10-15 22:00 ` Rafael J. Wysocki
2008-10-16 17:01 ` Brown, John M (WGBU R&D)
2008-10-16 19:31 ` Len Brown
2008-10-15 21:20 ` Rafael J. Wysocki
2008-11-22 11:11 ` Carlos Corbacho
2008-11-22 12:56 ` Rafael J. Wysocki
2008-10-16 9:13 ` Pavel Machek
2008-10-16 9:12 ` Pavel Machek
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=48F80F6F.6090608@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=john.brown3@hp.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
/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.