From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: Hugo Mills <hugo-lkml@carfax.org.uk>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Spurious completions during NCQ
Date: Thu, 06 Mar 2008 14:56:27 +0900 [thread overview]
Message-ID: <47CF878B.8090101@gmail.com> (raw)
In-Reply-To: <47B6EE53.1070101@rtr.ca>
Mark Lord wrote:
> Tejun, have the spurious completion fixes been backported
> to 2.6.23 / 2.6.22 yet ? Those kernels will be in common use
> for some time to come, and this fix is more or less essential.
Not that I know of. I'm prepping patches now.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-03-06 5:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 13:46 Spurious completions during NCQ Hugo Mills
2008-02-15 15:00 ` Calvin Walton
2008-02-15 15:04 ` Hugo Mills
2008-02-15 15:37 ` Michael Tokarev
2008-02-16 14:08 ` Mark Lord
2008-03-06 5:56 ` Tejun Heo [this message]
2008-03-06 6:05 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-10-13 13:12 Marco Lamberto
2007-09-07 17:57 Sumanth J.V
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=47CF878B.8090101@gmail.com \
--to=htejun@gmail.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.