public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: regarding ACPI support in 2.6.21
Date: Mon, 12 Mar 2007 11:03:49 -0400	[thread overview]
Message-ID: <45F56BD5.6040408@garzik.org> (raw)
In-Reply-To: <20070312154649.5f661a39@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>> I think it might be better to give up ACPI support in 2.6.21 and target
>> 2.6.22.  What do you think?
> 
> I removed it from my tree already so that I can actually use libata and
> do real work. The "crash every non PCI controller" feature in the current
> ACPI hacks means PCMCIA and ISAPnP do not work any more with libata.

It sounds like your tree is out-of-date.  Your patch to fix that went in 
days ago, applied by Linus directly:

commit ca4266359d0c1199af088447f209ab5bcc32a989
Author: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date:   Thu Mar 8 23:13:50 2007 +0000

      [PATCH] libata-acpi: Try and stop all the non PCI devices crashing


> In its current state it should be disabled, its broken, its wrong.

Does the above change your opinion any?

I lean towards disabling it by default in 2.6.21 anyway, but am 
interested in hearing an updated opinion on what's actually in the 
public tree.

	Jeff



  reply	other threads:[~2007-03-12 15:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 14:32 regarding ACPI support in 2.6.21 Tejun Heo
2007-03-12 15:46 ` Alan Cox
2007-03-12 15:03   ` Jeff Garzik [this message]
2007-03-12 17:01     ` Alan Cox

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=45F56BD5.6040408@garzik.org \
    --to=jeff@garzik.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@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