linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: V VS <v.vvsrini@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: Linux 2.6 SATA NCQ support
Date: Thu, 25 Jan 2007 07:44:14 -0500	[thread overview]
Message-ID: <45B8A61E.4010504@garzik.org> (raw)
In-Reply-To: <45B89EC8.8060602@gmail.com>

Tejun Heo wrote:
> V VS wrote:
>> Can you  please give us your inputs on why the NCQ depth is not getting
>> set correctly? Should we be looking at any other place for fixing this
>> problem?
> 
> Please give a shot at 2.6.20-rc5.  There was a related bug fix for ahci.

2.6.20-rc6 also has a couple fixes, and is worth a try.

	Jeff




      parent reply	other threads:[~2007-01-25 12:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <25b3869e0701250407q7fc6996eua411aeaec5a67444@mail.gmail.com>
2007-01-25 12:12 ` Linux 2.6 SATA NCQ support Tejun Heo
     [not found]   ` <25b3869e0701250419p7bcd41a4g38c05722df416115@mail.gmail.com>
2007-01-25 12:28     ` Tejun Heo
2007-01-25 12:44   ` 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=45B8A61E.4010504@garzik.org \
    --to=jeff@garzik.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=v.vvsrini@gmail.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).