netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org
Subject: Re: What's new in wireless-dev?
Date: Wed, 12 Jul 2006 08:48:32 -0400	[thread overview]
Message-ID: <20060712124827.GB4213@tuxdriver.com> (raw)
In-Reply-To: <20060712114832.4f1dbac6@griffin.suse.cz>

On Wed, Jul 12, 2006 at 11:48:32AM +0200, Jiri Benc wrote:
> On Tue, 11 Jul 2006 16:45:58 -0400, John W. Linville wrote:
> > John W. Linville:
> >       d80211: use netif_tx_lock API
> 
> > --- a/net/d80211/ieee80211.c
> > +++ b/net/d80211/ieee80211.c
> > @@ -1338,7 +1338,7 @@ static void ieee80211_tx_pending(unsigne
> >  	struct ieee80211_txrx_data tx;
> >  	int i, ret, reschedule = 0;
> >  
> > -	spin_lock_bh(&dev->xmit_lock);
> > +	netif_tx_lock_bh(dev);
> >  	dev->xmit_lock_owner = smp_processor_id();
> 
> Those dev->xmit_lock_owner assignments are done in netif_tx_[un]lock_bh,
> so they should go away as well.

Doh!  I missed that...thanks for the heads-up!

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2006-07-12 12:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 20:45 What's new in wireless-dev? John W. Linville
2006-07-12  9:48 ` Jiri Benc
2006-07-12 12:48   ` John W. Linville [this message]
2006-07-13  2:30     ` John W. Linville
  -- strict thread matches above, loose matches on Subject: below --
2006-09-05  0:10 John W. Linville
2006-09-05  0:02 John W. Linville
2006-09-04 23:53 John W. Linville
2006-08-24 19:08 John W. Linville
2006-08-08 23:41 John W. Linville
2006-07-30  1:30 John W. Linville
2006-06-15 21:10 John W. Linville

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=20060712124827.GB4213@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jbenc@suse.cz \
    --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).