From: Tejun Heo <htejun@gmail.com>
To: maximilian attems <max@stro.at>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org,
Chuck Short <zulcss@ubuntu.com>,
Tim Gardner <tim.gardner@canonical.com>
Subject: Re: [PATCH] ata: blacklist FUJITSU MHW2160BH PL
Date: Tue, 10 Jun 2008 16:29:37 +0900 [thread overview]
Message-ID: <484E2D61.8000604@gmail.com> (raw)
In-Reply-To: <20080610071903.GA24102@stro.at>
maximilian attems wrote:
> On Tue, 10 Jun 2008, Tejun Heo wrote:
>
>> maximilian attems wrote:
>>> From: Chuck Short <zulcss@ubuntu.com>
>>>
>>> OriginalAuthor: Chuck Short <zulcss@ubuntu.com>
>>> Bug: #175834
>> OSDL bz #175834 does not exist and even if it did having some
>> explanation on patch itself wouldn't hurt.
Eh... spurious completion check itself was spurious and got removed, so
the patch is not necessary.
Thanks.
--
tejun
prev parent reply other threads:[~2008-06-10 7:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 16:53 [PATCH] ata: blacklist FUJITSU MHW2160BH PL maximilian attems
2008-06-10 2:47 ` Tejun Heo
2008-06-10 7:19 ` maximilian attems
2008-06-10 7:29 ` Tejun Heo [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=484E2D61.8000604@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=max@stro.at \
--cc=tim.gardner@canonical.com \
--cc=zulcss@ubuntu.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).