netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jgarzik@pobox.com
Cc: herbert@gondor.apana.org.au, akpm@linux-foundation.org,
	netdev@vger.kernel.org, adaplas@pol.net
Subject: Re: [SC92031]: Fix priv->lock context
Date: Mon, 09 Apr 2007 12:07:08 -0700 (PDT)	[thread overview]
Message-ID: <20070409.120708.35442163.davem@davemloft.net> (raw)
In-Reply-To: <461A8D9D.6070604@pobox.com>

From: Jeff Garzik <jgarzik@pobox.com>
Date: Mon, 09 Apr 2007 15:01:49 -0400

> David Miller wrote:
> > From: Herbert Xu <herbert@gondor.apana.org.au>
> > Date: Fri, 6 Apr 2007 07:57:03 +1000
> > 
> >> On Thu, Apr 05, 2007 at 09:59:29AM -0700, David Miller wrote:
> >>> Where is the patch? :-)
> >>>
> >>> Second time you've done this in two days Herbert, tsk tsk :)))
> >> The patch was so easy that it was left as an exercise to the reader :)
> >>
> >> [SC92031]: Fix priv->lock context
> >>
> >> The spin_lock calls made in dev->open and dev->close must disable
> >> BH since open/close are made in process context.  Conversely, the
> >> call in dev->hard_start_xmit does not need to disable BH since it
> >> is already executing with BH disabled.
> >>
> >> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> > 
> > Applied, either Jeff or myself will make sure this gets into
> > Linus's tree.
> 
> Sounds like you got this one?

Yep.

      reply	other threads:[~2007-04-09 19:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05  2:04 Fw: Re: 2.6.21-rc5-mm4 Andrew Morton
2007-04-05 11:44 ` [SC92031]: Fix priv->lock context (was: 2.6.21-rc5-mm4) Herbert Xu
2007-04-05 16:59   ` [SC92031]: Fix priv->lock context David Miller
2007-04-05 21:57     ` Herbert Xu
2007-04-06  1:10       ` Antonino A. Daplas
2007-04-09 18:56       ` David Miller
2007-04-09 19:01         ` Jeff Garzik
2007-04-09 19:07           ` David Miller [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=20070409.120708.35442163.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adaplas@pol.net \
    --cc=akpm@linux-foundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jgarzik@pobox.com \
    --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).