From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Robert Hancock <hancockrwd@gmail.com>,
ide <linux-ide@vger.kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH #upstream] sata_sil24: always set protocol override for non-ATAPI data commands
Date: Sat, 22 Aug 2009 11:28:07 -0400 [thread overview]
Message-ID: <4A900E87.5060207@rtr.ca> (raw)
In-Reply-To: <4A900DE6.2020802@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> On 08/22/2009 10:03 AM, Mark Lord wrote:
..
>>> Hasn't this gone upstream yet??
>>> Heck, it should even go out for -stable, too.
>>
>> It's queued for 2.6.32... I'd rather be more conservative and get
>> wider testing before pushing such a fundamental change to sata_sil24
>> data xfer path upon everyone.
> ..
>
> Whatever. It's very well tested (and in continuous use) here on two systems
> with siI-3132 controllers. So we'll want to hear from users of the 3124
> and 3131/3531 chips for completeness, then.
..
Mmm.. I wonder if something like this patch might also be applicable
to the sata_sil.c driver too?
I've got a couple of those chips around here someplace,
so maybe I'll give that a spin.
next prev parent reply other threads:[~2009-08-22 15:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 20:11 [PATCH #upstream] sata_sil24: always set protocol override for non-ATAPI data commands Robert Hancock
2009-07-30 20:18 ` Mark Lord
2009-07-30 20:53 ` Jeff Garzik
2009-07-31 1:20 ` Tejun Heo
2009-08-22 5:57 ` Robert Hancock
2009-08-22 14:03 ` Mark Lord
2009-08-22 14:11 ` Jeff Garzik
2009-08-22 15:25 ` Mark Lord
2009-08-22 15:28 ` Mark Lord [this message]
2009-08-22 16:10 ` Jeff Garzik
2009-08-22 16:27 ` Robert Hancock
2009-08-22 16:02 ` Jeff Garzik
2009-08-22 16:30 ` 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=4A900E87.5060207@rtr.ca \
--to=liml@rtr.ca \
--cc=hancockrwd@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).