From: Len Brown <lenb@kernel.org>
To: "Brown, John M (WGBU R&D)" <john.brown3@hp.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
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: Wed, 15 Oct 2008 17:49:50 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0810151746460.3026@localhost.localdomain> (raw)
In-Reply-To: <C075D3D77BA5EF4FBB0939047B182ABF25C79AD3EE@GVW1144EXB.americas.hpqcorp.net>
Matthew,
You are right, of course, we're not doing something right
if a new machine needs this workaround.
However, we don't yet know what we're not doing right:-)
Until we figure that out, the blacklist is a practical way
forward. There have been several cases in the past where
we grew a blacklist -- some of them quite large,
before we figured out what bug-compatibility
magic we needed in order to delete the blacklist.
I'm hopeful the same story will play out here.
applied.
thanks,
-Len
next prev parent reply other threads:[~2008-10-15 21:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 20:54 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 [this message]
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
[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
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=alpine.LFD.1.10.0810151746460.3026@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=john.brown3@hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®