From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: commit a258f183ee4e48e9352b408e8448467eebdc6cd2
Date: Wed, 02 Jan 2008 18:34:38 +0900 [thread overview]
Message-ID: <477B5AAE.7070008@gmail.com> (raw)
Happy new year, Jeff, Alan.
I'm curious why commit a258f183 got in? We already deal with this
problem by executing SETXFER by polling. That's better IMHO for two
reasons - no clutter in hot path && applies to drivers which use custom
interrupt handlers.
Thanks.
--
tejun
next reply other threads:[~2008-01-02 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 9:34 Tejun Heo [this message]
2008-01-02 13:48 ` commit a258f183ee4e48e9352b408e8448467eebdc6cd2 Alan Cox
2008-01-02 14:24 ` Tejun Heo
2008-01-02 14:19 ` Alan Cox
2008-01-02 14:33 ` Tejun Heo
2008-01-02 15:18 ` Alan Cox
2008-01-02 15:52 ` 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=477B5AAE.7070008@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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).