linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nate Case <ncase@xes-inc.com>
To: Sebastian Siewior <netdev@ml.breakpoint.cc>
Cc: netdev@vger.kernel.org, linuxppc-dev@ozlabs.org,
	Vitaly Bordug <vbordug@ru.mvista.com>,
	Li Yang <leoli@freescale.com>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH / RFC] net: don't grab a mutex within a timer context in gianfar
Date: Fri, 25 Jul 2008 09:16:00 -0500	[thread overview]
Message-ID: <1216995360.7559.1022.camel@localhost.localdomain> (raw)
In-Reply-To: <20080723200337.GA5122@Chamillionaire.breakpoint.cc>

On Wed, 2008-07-23 at 22:03 +0200, Sebastian Siewior wrote:
> I moved it into a workqueue, this is what tg3 does.
> I would convert the other three drivers unless $dude suggests a better
> method or somebody else takes care....
> 
>  drivers/net/gianfar.c |   22 ++++++++++++++++++----
>  drivers/net/gianfar.h |    2 ++
>  2 files changed, 20 insertions(+), 4 deletions(-)

This looks good to me.

-- 
Nate Case <ncase@xes-inc.com>

  reply	other threads:[~2008-07-25 14:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 12:10 bug: mutex_lock() in interrupt conntext via phy_stop() in gianfar Sebastian Siewior
2008-07-21 22:57 ` Nate Case
2008-07-22 20:59   ` Sebastian Siewior
2008-07-23 20:03     ` [PATCH / RFC] net: don't grab a mutex within a timer context " Sebastian Siewior
2008-07-25 14:16       ` Nate Case [this message]
2008-07-25 19:02       ` Andy Fleming
2008-07-23 22:12   ` bug: mutex_lock() in interrupt conntext via phy_stop() " Benjamin Herrenschmidt
2008-07-24  7:27     ` Sebastian Siewior
2008-07-22  7:54 ` Wolfram Sang

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=1216995360.7559.1022.camel@localhost.localdomain \
    --to=ncase@xes-inc.com \
    --cc=jgarzik@pobox.com \
    --cc=leoli@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@ml.breakpoint.cc \
    --cc=netdev@vger.kernel.org \
    --cc=vbordug@ru.mvista.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).