linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: "Grover, Andrew" <andrew.grover@intel.com>,
	marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [BK PATCH] ACPI updates
Date: Wed, 4 Dec 2002 12:58:52 +0000	[thread overview]
Message-ID: <20021204125852.GE647@suse.de> (raw)
In-Reply-To: <20021203184705.A23371@devserv.devel.redhat.com>

On Tue, Dec 03, 2002 at 06:47:05PM -0500, Arjan van de Ven wrote:
 > On Tue, Dec 03, 2002 at 03:29:56PM -0800, Grover, Andrew wrote:
 > > Well maybe that's what we should do - use the UnitedLinux ACPI patch (which
 > 
 > No. What UL did was to put back the code you remove. YOU can do that
 > better I'm sure, since you actively remove it in your patch;
 > just not doing that is obviously simpler...

There's also a few other things in the UL patch Andi did iirc,
things like 'dont use ACPI if the BIOS date is <2000', which seems
to be a good universal crap-acpi-bios detector. (You can still override
this with a bootarg iirc)

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2002-12-04 12:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 23:29 [BK PATCH] ACPI updates Grover, Andrew
2002-12-03 23:47 ` Arjan van de Ven
2002-12-04 12:58   ` Dave Jones [this message]
2002-12-05 17:06 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2003-05-24  0:15 Grover, Andrew
2002-12-06  1:36 Grover, Andrew
2002-12-06 16:50 ` Pavel Machek
2002-12-03 18:39 Grover, Andrew
2002-12-03 19:31 ` Alan Cox
2002-12-03 23:00 ` Arjan van de Ven
2002-12-02 19:29 Grover, Andrew
2002-12-03  9:31 ` Arjan van de Ven

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=20021204125852.GE647@suse.de \
    --to=davej@codemonkey.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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;
as well as URLs for NNTP newsgroup(s).