linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, Mark Lord <kernel@teksavvy.com>,
	Seed <seedrubbish@gmail.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	stable@kernel.org
Subject: Re: [PATCH #upstream-fixes] libahci: fix result_tf handling after an ATA PIO data-in command
Date: Fri, 15 Oct 2010 10:45:17 +0200	[thread overview]
Message-ID: <4CB8149D.4050707@kernel.org> (raw)
In-Reply-To: <AANLkTi=FDPbo28+RL8FyY1v8O0kSac=snPMegV0bkz83@mail.gmail.com>

Hello,

On 10/15/2010 02:32 AM, Robert Hancock wrote:
>> +       if (qc->tf.protocol == ATA_PROT_PIO && qc->dma_dir == DMA_FROM_DEVICE &&
>> +           !(qc->flags & ATA_QCFLAG_FAILED))
>> +               qc->result_tf.command = (rx_fis + RX_FIS_PIO_SETUP)[15];
> 
> Shouldn't we be reading the entire TF from the PIO setup FIS and then
> just replacing the command register value with the E_Status field? It
> looks like that's the only field in the TF that's being set here.

Hmmm, yeah, probably that would be better.  I'll post the updated
version soon.

Thanks.

-- 
tejun

  reply	other threads:[~2010-10-15  8:45 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24  5:34 [BUG] libahci returns stale result tf much of the time Mark Lord
2010-09-24  5:49 ` Seed
2010-09-24  6:27   ` Mark Lord
2010-09-24  7:01     ` Seed
2010-09-24 13:11       ` Mark Lord
2010-09-24 13:24         ` Mark Lord
2010-09-24 23:26           ` Robert Hancock
2010-10-04  9:18             ` Tejun Heo
2010-10-04 17:01               ` Mark Lord
2010-10-04 17:06                 ` Mark Lord
2010-10-04 17:31                   ` Mark Lord
2010-10-04 18:50                     ` Mark Lord
2010-10-04 19:27                       ` Jeff Garzik
2010-10-04 19:35                         ` Mark Lord
2010-10-04 19:42                           ` Jeff Garzik
2010-10-04 19:51                             ` Mark Lord
2010-10-05  7:07                               ` Tejun Heo
2010-10-05 14:06                                 ` Mark Lord
2010-10-05 16:06                                   ` Tejun Heo
2010-10-06  1:00                                     ` Robert Hancock
2010-10-14  8:53                                       ` [PATCH #upstream-fixes] libahci: fix result_tf handling after an ATA PIO data-in command Tejun Heo
2010-10-14 21:38                                         ` Mark Lord
2010-10-15  0:24                                           ` Robert Hancock
2010-10-15  8:45                                             ` Tejun Heo
2010-10-15 22:14                                               ` Mark Lord
2010-10-15  0:32                                         ` Robert Hancock
2010-10-15  8:45                                           ` Tejun Heo [this message]
2010-10-15  9:00                                         ` [PATCH UPDATED " Tejun Heo

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=4CB8149D.4050707@kernel.org \
    --to=tj@kernel.org \
    --cc=hancockrwd@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=kernel@teksavvy.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=seedrubbish@gmail.com \
    --cc=stable@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).