From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
len.brown@intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: libata-acpi: allow _GTF on SATA, but disable on PATA for now
Date: Mon, 12 Mar 2007 09:55:28 -0700 [thread overview]
Message-ID: <20070312095528.3dd7a693.kristen.c.accardi@intel.com> (raw)
In-Reply-To: <20070310164059.4ba68bcc@lxorguk.ukuu.org.uk>
On Sat, 10 Mar 2007 16:40:59 +0000
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Instead merge the one that fixe the non PCI
> crashes and we might get further.
In bugzilla #7907 you could post your patch and see if the reporters there
can at least confirm that it fixes their problem.
Meanwhile, to solve the problem for these people, and without introducing
a lot of new code at this stage in the release, perhaps you can suggest
a more accurate way to detect PATA vs. SATA so we can fix the bug? Either
that or Len should drop the ATA ACPI support from 2.6.21 altogether and
we should try to coordinate our efforts better for 2.6.22. The alternative
to dropping the ACPI support is to set the default for libata.acpi to off.
Thanks,
Kristen
next prev parent reply other threads:[~2007-03-12 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200703100559.l2A5x6kP017578@hera.kernel.org>
2007-03-10 11:30 ` Jeff Garzik
2007-03-10 16:40 ` Alan Cox
2007-03-12 16:55 ` Kristen Carlson Accardi [this message]
2007-03-12 22:00 ` Alan Cox
2007-03-12 21:11 ` Kristen Carlson Accardi
2007-03-11 3:14 ` Len Brown
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=20070312095528.3dd7a693.kristen.c.accardi@intel.com \
--to=kristen.c.accardi@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--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
all inboxes | Powered by JetHome®