mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tear <tarrqt@yahoo.com>,
	mingo@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Brown, Len" <len.brown@intel.com>
Subject: Re: [RFC][PATCH] IO-APIC blacklist
Date: Sat, 2 Jun 2007 15:54:40 -0700	[thread overview]
Message-ID: <20070602155440.c1f8d1cb.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.98.0706021400330.23741@woody.linux-foundation.org>

On Sat, 2 Jun 2007 14:28:58 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote:

> That blacklist entry is _ancient_. It's entirely possible that it's just 
> bogus: we've had so many ACPI fixes since it was added, that it's quite 
> possible that the blacklist entry itself is bogus, and is the result of 
> some old ACPI bug that triggered on that entry.
> 
> The Dell GX240 entry was added by commit 68e4ad79294 in the historic Linux 
> archive:
> 
>     Author: Len Brown <len.brown@intel.com>
>     Date:   Sat Aug 9 15:00:59 2003 -0400
> 
>     ACPI from 2.4:
>     build: add ACPI_HT, delete ACPI_HT_ONLY
>     boot: add acpi={force, off, ht}; delete "noht", "acpismp="
>     add DMI blacklist from UnitedLinux
> 
> and since it sounds like the machine _works_ with ACPI on, my real 
> preference would be to just remove the black-list entry.
> 
> In fact, I thought that patch already existed in the -mm tree?

It is.  remove-dell-optiplex-gx240-from-the-acpi-blacklist.patch

> Len - do you have any archives back from 2003 and earlier to indicate why 
> the Dell GX240 was blacklisted?

"add DMI blacklist from UnitedLinux".  Lost in the mists of time, I expect.

I guess we can tag remove-dell-optiplex-gx240-from-the-acpi-blacklist.patch
as "backport to 2.6.22.x if it doesn't break anything in 2.6.23-rcX".

  reply	other threads:[~2007-06-02 22:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 14:10 Tear
2007-06-02 14:39 ` Heikki Orsila
2007-06-02 16:39 ` Linus Torvalds
2007-06-02 20:32   ` Tear
2007-06-02 21:28     ` Linus Torvalds
2007-06-02 22:54       ` Andrew Morton [this message]
2007-06-02 23:13       ` Len Brown
2007-06-02 23:33       ` Len Brown
2007-06-02 23:53       ` Tear
2007-06-03  4:16         ` Len Brown
2007-06-03 10:24           ` Tear
2007-06-03 11:25           ` Tear
2007-06-02 17:46 ` Len Brown
2007-06-02 20:39   ` Tear
2007-06-02 20:55     ` Linus Torvalds
2007-06-02 23:48       ` Tear

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=20070602155440.c1f8d1cb.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tarrqt@yahoo.com \
    --cc=torvalds@linux-foundation.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 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®