From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mark Lord <liml@rtr.ca>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Flexible SFF interrupt handling
Date: Fri, 30 Nov 2007 10:11:12 +0900 [thread overview]
Message-ID: <474F6330.8040400@gmail.com> (raw)
In-Reply-To: <474F6280.8090403@gmail.com>
Tejun Heo wrote:
> And when reading off Status when idle, we'll need to return 0 from
> irq_handler. That will prevent IRQ screaming IRQ lock and nobody cared
That sentence was "That will prevent IRQ screaming from causing IRQ live
lock..." in my mind. Some packets were lost while transmitting it via
my neck, arms and finally through my fingertips and my fingers foolishly
didn't ask for retransmission. :-P
--
tejun
prev parent reply other threads:[~2007-11-30 1:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-28 13:45 Flexible SFF interrupt handling Jeff Garzik
2007-11-28 14:29 ` Alan Cox
2007-11-28 16:09 ` Jeff Garzik
2007-11-28 14:33 ` Mark Lord
2007-11-28 15:58 ` Jeff Garzik
2007-11-28 16:48 ` Mark Lord
2007-11-28 17:00 ` Mark Lord
2007-11-30 1:08 ` Tejun Heo
2007-11-30 1:11 ` 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=474F6330.8040400@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--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).