mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Tony Luck" <tony.luck@intel.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Taku Izumi" <izumi.taku@jp.fujitsu.com>,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST
Date: Tue, 27 May 2008 16:41:59 -0700	[thread overview]
Message-ID: <12c511ca0805271641r68d50d3do9f6427a8dc6ad469@mail.gmail.com> (raw)
In-Reply-To: <20080527162029.e549a226.akpm@linux-foundation.org>

I'm not sure that sharing drivers/acpi/blacklist.c between different
architectures is wise idea.  There are entries in there that make
blanket decisions for all machines made by an OEM.

It seems quite possible that an OEM that makes boxes using
different processor architectures might make different mistakes
in the respective BIOS teams.

-Tony

  reply	other threads:[~2008-05-27 23:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4816F9B9.3090609@jp.fujitsu.com>
2008-05-23  6:36 ` [PATCH 0/2] ACPI: add "OSI(Linux) checking procedure" for ia64 machines Taku Izumi
2008-05-23  6:39   ` [PATCH 1/2] ACPI: add acpi_osi_dmi_table evaluation procedure " Taku Izumi
2008-05-23  6:43   ` [PATCH 2/2] ACPI: add DMI info to enable OSI(Linux) on PRIMEQUEST Taku Izumi
2008-05-25 11:43     ` Pavel Machek
2008-05-26  7:56       ` Taku Izumi
2008-05-26  8:06         ` Pavel Machek
2008-05-27  1:13           ` KAMEZAWA Hiroyuki
2008-05-27  2:05             ` Arjan van de Ven
2008-05-27 23:20     ` Andrew Morton
2008-05-27 23:41       ` Tony Luck [this message]
2008-05-27 23:50         ` Andrew Morton
2008-05-28  4:04           ` Luck, Tony
2008-05-28  0:09       ` KAMEZAWA Hiroyuki

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=12c511ca0805271641r68d50d3do9f6427a8dc6ad469@mail.gmail.com \
    --to=tony.luck@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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®