From: Len Brown <lenb@kernel.org>
To: Thomas Renninger <trenn@suse.de>
Cc: akpm@linux-foundation.org, linux-acpi@vger.kernel.org,
mjg59@srcf.ucam.org, arekm@maven.pl, feng.tang@intel.com,
flinco@libero.it, mad_soft@inbox.ru, mjg@redhat.com, rjw@sisk.pl
Subject: Re: [patch 7/7] acpi: remove old blacklist entries
Date: Sun, 14 Mar 2010 16:35:24 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1003141610020.18869@sony> (raw)
In-Reply-To: <201002231211.54403.trenn@suse.de>
On Tue, 23 Feb 2010, Thomas Renninger wrote:
> > - {
> > - .callback = force_acpi_ht,
> > - .ident = "IBM eserver xSeries 330",
> > - .matches = {
> > - DMI_MATCH(DMI_BOARD_VENDOR, "IBM"),
> > - DMI_MATCH(DMI_BOARD_NAME, "eserver xSeries 330"),
> > - },
> > - },
> For this one I can confirm that the blacklist is not needed with latest
> kernel and the BIOS I use.
...
> I'd also vote to remove the blacklist for ACPI test
> (does this branch get synced into linux-next)?
Thanks for the verification, Thomas.
Yes, this one is gone, with all the other force_acpi_ht entries.
Yes, the acpi test branch is included in linux-next.
cheers,
Len Brown, Intel Open Source Technology Center
prev parent reply other threads:[~2010-03-15 1:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 22:37 [patch 7/7] acpi: remove old blacklist entries akpm
2010-02-03 23:04 ` Henrique de Moraes Holschuh
2010-02-16 7:53 ` Len Brown
2010-02-16 8:19 ` Len Brown
2010-02-16 15:40 ` Matthew Garrett
2010-02-17 2:49 ` Len Brown
2010-02-17 14:32 ` Matthew Garrett
2010-02-17 18:24 ` Len Brown
2010-02-17 18:31 ` Matthew Garrett
2010-02-17 19:43 ` Henrique de Moraes Holschuh
2010-02-17 21:23 ` Len Brown
2010-02-17 21:28 ` Matthew Garrett
2010-02-19 5:44 ` Len Brown
2010-02-19 5:53 ` [PATCH 1/2] ACPI: remove "acpi=ht" DMI blacklist Len Brown
2010-02-19 5:55 ` [patch 2/2] ACPI: delete the "acpi=ht" boot option Len Brown
2010-02-23 11:11 ` [patch 7/7] acpi: remove old blacklist entries Thomas Renninger
2010-03-14 20:35 ` Len Brown [this message]
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.2.00.1003141610020.18869@sony \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arekm@maven.pl \
--cc=feng.tang@intel.com \
--cc=flinco@libero.it \
--cc=linux-acpi@vger.kernel.org \
--cc=mad_soft@inbox.ru \
--cc=mjg59@srcf.ucam.org \
--cc=mjg@redhat.com \
--cc=rjw@sisk.pl \
--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