linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Tejun Heo <htejun@gmail.com>
Cc: Mark Lord <liml@rtr.ca>, Mark Lord <lkml@rtr.ca>,
	Jeff Garzik <jeff@garzik.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS
Date: Tue, 2 Oct 2007 17:40:23 +0200	[thread overview]
Message-ID: <20071002174023.0a70a93e@localhost> (raw)
In-Reply-To: <47020D12.5090402@gmail.com>

On Tue, 02 Oct 2007 18:19:14 +0900
Tejun Heo <htejun@gmail.com> wrote:

> Yeah, "World's first" is a pretty good clue indicating "broken".
> Blacklisting it seems like a good idea after all.

OT: I cannot test anything NCQ related for a while because the Intel
Mobo departed yesterday, so I'm on a different board without NCQ
support  ;)

-- 
	Paolo Ornati
	Linux 2.6.23-rc8generic-ga64314e6 on x86_64

      reply	other threads:[~2007-10-02 13:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070930160548.235be972@localhost>
     [not found] ` <46FFAFE1.2010302@gmail.com>
2007-09-30 14:42   ` [PATCH] blacklist NCQ on Seagate Barracuda ST380817AS Paolo Ornati
     [not found] ` <20070930152908.1f58d39d@the-village.bc.nu>
2007-09-30 14:46   ` Paolo Ornati
2007-09-30 15:05     ` Jeff Garzik
2007-09-30 15:28       ` Paolo Ornati
2007-09-30 15:43         ` Jeff Garzik
2007-09-30 15:52           ` Paolo Ornati
2007-09-30 15:59             ` Jeff Garzik
2007-09-30 16:03               ` Paolo Ornati
2007-09-30 17:26       ` Mark Lord
2007-09-30 17:29         ` Tejun Heo
2007-09-30 17:43           ` Mark Lord
2007-09-30 17:51             ` Tejun Heo
2007-09-30 18:54               ` Mark Lord
2007-09-30 19:01                 ` Mark Lord
2007-10-02  9:19                   ` Tejun Heo
2007-10-02 15:40                     ` Paolo Ornati [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=20071002174023.0a70a93e@localhost \
    --to=ornati@fastwebnet.it \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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).