From: Jeff Garzik <jgarzik@pobox.com>
To: Brett Russ <russb@emc.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH libata-2.6] AHCI: fix fatal error int handling
Date: Thu, 10 Mar 2005 00:45:07 -0500 [thread overview]
Message-ID: <422FDEE3.5090306@pobox.com> (raw)
In-Reply-To: <20050309205714.DBED014FA3@lns1032.lss.emc.com>
Brett Russ wrote:
> I noticed that the AHCI CI (cmd issue) reg wasn't getting cleared
> after error ints resulting in no further commands being successfully
> issued to the port. This patch fixes. All that's really needed is
> the 1's complement but I also removed the disabling/enabling of the
> FIS_RX b/c this isn't spec'd as necessary when handling error ints.
>
> Signed-off-by: Brett Russ <russb@emc.com>
Thanks, applied.
prev parent reply other threads:[~2005-03-10 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 20:57 [PATCH libata-2.6] AHCI: fix fatal error int handling Brett Russ
2005-03-10 5:45 ` 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=422FDEE3.5090306@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russb@emc.com \
/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).