From: Timur Tabi <timur.tabi@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: David Miller <davem@davemloft.net>,
afleming@freescale.com, netdev@vger.kernel.org
Subject: Re: [PATCH] gianfar: Wait for both RX and TX to stop
Date: Wed, 21 Apr 2010 09:33:56 -0500 [thread overview]
Message-ID: <z2ged82fe3e1004210733v8fa40902k664549aa9620b13@mail.gmail.com> (raw)
In-Reply-To: <10AE27BE-1830-4AAD-83E6-20001BC430D8@kernel.crashing.org>
On Wed, Apr 21, 2010 at 7:17 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
> I understand, its more a sense that we are saying we want to time out for what I consider a catastrophic HW failure.
And how else will you detect and recover from such a failure without a
timeout? And are you absolutely certain that there will never be a
programming failure that will cause this loop to spin forever?
If you're really opposed to a timeout, you can still use
spin_event_timeout() by just setting the timeout to -1 and adding a
comment explaining why.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2010-04-21 14:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 23:13 [PATCH] gianfar: Wait for both RX and TX to stop Andy Fleming
2010-04-19 21:08 ` Timur Tabi
2010-04-20 4:43 ` Kumar Gala
2010-04-20 15:01 ` Timur Tabi
2010-04-20 15:59 ` Timur Tabi
2010-04-21 1:06 ` David Miller
2010-04-21 4:22 ` Kumar Gala
2010-04-21 5:36 ` David Miller
2010-04-21 12:17 ` Kumar Gala
2010-04-21 14:33 ` Timur Tabi [this message]
2010-04-21 19:13 ` Kumar Gala
2010-04-21 21:33 ` David Miller
2010-04-20 4:44 ` Kumar Gala
2010-04-20 8:18 ` David Miller
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=z2ged82fe3e1004210733v8fa40902k664549aa9620b13@mail.gmail.com \
--to=timur.tabi@gmail.com \
--cc=afleming@freescale.com \
--cc=davem@davemloft.net \
--cc=galak@kernel.crashing.org \
--cc=netdev@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).