linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alan <alan@lxorguk.ukuu.org.uk>, Len Brown <lenb@kernel.org>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>
Subject: Re: ATA ACPI (was Re: Linux 2.6.21-rc5)
Date: Tue, 27 Mar 2007 14:54:42 +0900	[thread overview]
Message-ID: <4608B1A2.3040305@gmail.com> (raw)
In-Reply-To: <4608B0CA.1040005@garzik.org>

Jeff Garzik wrote:
> Linus Torvalds wrote:
>> There's various fixes here, ranging from some architecture updates 
>> (ia64, ARM, MIPS, SH, Sparc64) to KVM, networking and network drivers.
>>
>> And random one-liners.
>>
>> But probably more important, and likely much more visible to most 
>> people is the fixes for the fallout from the hrtimers and no-HZ 
>> changes, and some of the ACPI regressions.
>>
>> Those timer changes ended up much more painful than anybody wished 
>> for, but big thanks to Thomas Gleixner for being on it like a weasel 
>> on a dead rat, and the regression list has kept shrinking.
>>
>> So if you have reported a regression in the 2.6.21-rc series, please 
>> check 2.6.21-rc5, and update your report as appropriate (whether fixed 
>> or "still problems with xyzzy").
>>
>>         Linus
> 
> 
> [just got back from vacation, or would have sent this earlier]
> 
> FWIW, I'm still leaning towards disabling libata ACPI support by default 
> for 2.6.21.
> 
> Upstream has Alan's fix for the worst PATA problems, but for different 
> reasons, I think PATA ACPI and SATA ACPI support in libata does not feel 
> quite ready for prime time in 2.6.21.
> 
> Scream now, or hold your peace until 2.6.22... :)

I second disabling ACPI for 2.6.21.

-- 
tejun

  reply	other threads:[~2007-03-27  5:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0703251559560.6730@woody.linux-foundation.org>
2007-03-27  1:59 ` [2/5] 2.6.21-rc5: known regressions Adrian Bunk
2007-03-28 19:46   ` Laurent Riffard
2007-03-29 19:02     ` Fabio Comolli
2007-03-27  1:59 ` [4/5] " Adrian Bunk
2007-03-27  5:51 ` ATA ACPI (was Re: Linux 2.6.21-rc5) Jeff Garzik
2007-03-27  5:54   ` Tejun Heo [this message]
2007-03-27 21:32     ` Pavel Machek
2007-03-28  9:51       ` Tejun Heo
2007-03-27 17:07   ` Linus Torvalds
2007-03-27 18:48     ` Jeff Garzik
2007-03-30 21:32 ` [1/4] 2.6.21-rc5: known regressions (v2) Adrian Bunk
2007-03-30 21:38   ` Greg KH
2007-03-31  0:23   ` Michal Jaegermann
2007-03-31 15:01     ` Adrian Bunk
2007-03-31 16:42       ` Michal Jaegermann
2007-03-30 21:32 ` [3/4] " Adrian Bunk
2007-03-31  2:52   ` Jeff Chua
2007-03-31 18:19 ` 2.6.21-rc5: known regressions with patches (v2) Adrian Bunk
2007-04-03  4:05   ` [PATCH] libata: add NCQ blacklist entries from Silicon Image Windows driver (v2) Robert Hancock
2007-04-03  4:13     ` Tejun Heo
2007-04-04  6:09     ` Jeff Garzik
2007-04-04 14:26       ` Robert Hancock

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=4608B1A2.3040305@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=kristen.c.accardi@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).