From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Peer Chen <pchen@nvidia.com>,
zaceni2@yandex.ru
Subject: Re: [PATCH #upstream-fixes] ahci: force CAP_NCQ for earlier NV MCPs
Date: Mon, 13 Apr 2009 04:27:38 -0400 [thread overview]
Message-ID: <49E2F77A.5020502@garzik.org> (raw)
In-Reply-To: <49DD164B.6000809@kernel.org>
Tejun Heo wrote:
> Along with MCP65, MCP67 and 73 also don't set CAP_NCQ. Force it.
> Reported by zaceni@yandex.ru on bko#13014 and confirmed by Peer Chen.
>
> Signed-off-by: Tejun Heo <tj@kernel.org>
> Reported-by: NightFox <zaceni2@yandex.ru>
> Cc: Peer Chen <pchen@nvidia.com>
> ---
> drivers/ata/ahci.c | 57 ++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 33 insertions(+), 24 deletions(-)
>
> drivers/ata/ahci.c | 57 ++++++++++++++++++++++++++++++-----------------------
> 1 file changed, 33 insertions(+), 24 deletions(-)
applied
prev parent reply other threads:[~2009-04-13 8:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 21:25 [PATCH #upstream-fixes] ahci: force CAP_NCQ for earlier NV MCPs Tejun Heo
2009-04-13 8:27 ` 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=49E2F77A.5020502@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=tj@kernel.org \
--cc=zaceni2@yandex.ru \
/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).