From: Jason Riedy <jason@acm.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question)
Date: Sun, 03 May 2009 18:35:41 -0400 [thread overview]
Message-ID: <874ow1ak76.fsf@sparse.dyndns.org> (raw)
In-Reply-To: <49FE038F.2040704@gmail.com> (Robert Hancock's message of "Sun, 03 May 2009 14:50:23 -0600")
And Robert Hancock writes:
> Well, it's a potential concern, but it's simple enough I doubt it
> would really result in much of a burden.
My D620 is one of those that corrupted the file system with the
force-AHCI patch. If I hadn't applied the patch externally, I might
have guessed it was the file system code... Given all the churn in the
fs code right now, is it wise to add another *known* corruption vector?
Jason
next prev parent reply other threads:[~2009-05-03 23:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LzLgA-0004j6-9W@closure.thunk.org>
2009-04-30 2:27 ` No NCQ support on X61s Ultrabay? (Intel ICH8 SATA controller question) Jeff Garzik
2009-04-30 7:33 ` Alex Buell
2009-04-30 7:45 ` Tejun Heo
2009-04-30 13:47 ` Alan Cox
2009-04-30 15:35 ` Matthew Wilcox
2009-04-30 15:47 ` Matthew Garrett
2009-05-01 1:49 ` Robert Hancock
2009-05-03 2:07 ` Tejun Heo
2009-05-03 20:50 ` Robert Hancock
2009-05-03 22:35 ` Jason Riedy [this message]
2009-04-30 11:34 ` Theodore Tso
2009-04-30 11:38 ` Theodore Tso
2009-05-01 1:51 ` Robert Hancock
2009-05-01 2:51 ` Theodore Tso
2009-05-01 4:21 ` Robert Hancock
2009-05-01 11:35 ` Matthew Wilcox
2009-05-01 13:14 ` Theodore Tso
2009-05-01 13:59 ` Matthew Garrett
2009-05-01 14:09 ` Matthew Wilcox
2009-04-30 15:42 ` Henrique de Moraes Holschuh
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=874ow1ak76.fsf@sparse.dyndns.org \
--to=jason@acm.org \
--cc=hancockrwd@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).