netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur.tabi@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Andy Fleming <afleming@freescale.com>,
	davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] gianfar: Wait for both RX and TX to stop
Date: Tue, 20 Apr 2010 10:01:48 -0500	[thread overview]
Message-ID: <o2oed82fe3e1004200801n98683cdalb2898c879b93f8fd@mail.gmail.com> (raw)
In-Reply-To: <DD217C72-156B-403D-B83B-EB365C782F2B@kernel.crashing.org>

On Mon, Apr 19, 2010 at 11:43 PM, Kumar Gala <galak@kernel.crashing.org> wrote:

> spin_event_timeout doesn't make sense for this.  The patch is fine.

Can you please elaborate on that?  I don't understand why you think
that.  spin_event_timeout() takes an expression and a timeout, and
loops over the expression calling cpu_relax(), just like this loop
does.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2010-04-20 15:02 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 [this message]
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
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=o2oed82fe3e1004200801n98683cdalb2898c879b93f8fd@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).