From: Tejun Heo <htejun@gmail.com>
To: Tejun Heo <htejun@gmail.com>
Cc: jeff@garzik.org, alan@lxorguk.ukuu.org.uk, ric@emc.com,
edmudama@gmail.com, linux-ide@vger.kernel.org
Subject: Subject should be [PATCHSET] put some intelligence into speed down sequence
Date: Fri, 02 Feb 2007 16:10:31 +0900 [thread overview]
Message-ID: <45C2E3E7.7060509@gmail.com> (raw)
In-Reply-To: <11704001701015-git-send-email-htejun@gmail.com>
Eek, sorry.
--
tejun
next prev parent reply other threads:[~2007-02-02 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 7:09 [PATCHSET] ata_piix: improve combined mode handling Tejun Heo
2007-02-02 7:09 ` [PATCH 2/5] libata: improve probe failure handling Tejun Heo
2007-02-02 7:09 ` [PATCH 1/5] libata: improve ata_down_xfermask_limit() Tejun Heo
2007-02-02 7:09 ` [PATCH 4/5] libata: kill ATA_DNXFER_ANY Tejun Heo
2007-02-02 7:09 ` [PATCH 5/5] ahci: consider SDB FIS containing spurious NCQ completions HSM violation Tejun Heo
2007-02-02 7:09 ` [PATCH 3/5] libata: put some intelligence into EH speed down sequence Tejun Heo
2007-02-02 7:10 ` Tejun Heo [this message]
2007-02-02 7:12 ` Please ignore this thread. I'll resend Tejun Heo
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=45C2E3E7.7060509@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=edmudama@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=ric@emc.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).