From: Jeff Garzik <jeff@garzik.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] sata_fsl: Fix the command description of FSL SATA controller
Date: Fri, 15 May 2009 14:16:54 -0400 [thread overview]
Message-ID: <4A0DB196.8010209@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0905140945540.8378@localhost.localdomain>
Kumar Gala wrote:
> From: Dave Liu <daveliu@freescale.com>
>
> The bit 11 of command description is reserved bit in Freescale
> SATA controller and needs to be set to '1'. This is needed to
> make sure the last write from the controller to the buffer
> descriptor is seen before an interrupt is raised.
>
> Signed-off-by: Dave Liu <daveliu@freescale.com>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
>
> Jeff, please pick this up as a bug fix for 2.6.30
>
> drivers/ata/sata_fsl.c | 8 +++++---
> 1 files changed, 5 insertions(+), 3 deletions(-)
applied
prev parent reply other threads:[~2009-05-15 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 14:47 [PATCH] sata_fsl: Fix the command description of FSL SATA controller Kumar Gala
2009-05-15 18:16 ` Jeff Garzik [this message]
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=4A0DB196.8010209@garzik.org \
--to=jeff@garzik.org \
--cc=galak@kernel.crashing.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).