From: Tejun Heo <htejun@gmail.com>
To: "\"J.A. Magallón\"" <jamagallon@ono.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1]
Date: Mon, 26 Mar 2007 20:01:52 +0900 [thread overview]
Message-ID: <4607A820.60103@gmail.com> (raw)
In-Reply-To: <20070326022420.224cc4f2@werewolf-wl>
J.A. Magallón wrote:
> Libata seems to misdetect my cable.
> I have double-checked and the cable is 80 pin...
Does the following patch fix your problem?
http://article.gmane.org/gmane.linux.ide/17444
(You can get the raw message by appending /raw to the URL).
--
tejun
next prev parent reply other threads:[~2007-03-26 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070319205623.299d0378.akpm@linux-foundation.org>
2007-03-26 0:24 ` Wrong IDE cable detection in libata [Re: 2.6.21-rc4-mm1] J.A. Magallón
2007-03-26 11:01 ` Tejun Heo [this message]
2007-03-26 20:18 ` J.A. Magallón
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=4607A820.60103@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jamagallon@ono.com \
--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 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).