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 22:30:22 -0400 [thread overview]
Message-ID: <20060713023017.GA16084@tuxdriver.com> (raw)
In-Reply-To: <20060712124827.GB4213@tuxdriver.com>
On Wed, Jul 12, 2006 at 08:48:32AM -0400, John W. Linville wrote:
> 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!
[PATCH] d80211: remove referencess to xmit_lock_owner
Clean-up sloppy attempt at moving to netif_tx_lock API. When using that
API, direct manipulation of xmit_lock_owner is unnecessary and
inappropriate.
Signed-off-by: John W. Linville <linville@tuxdriver.com>
---
net/d80211/ieee80211.c | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
a5b83f260b3cbe9ed161313e620c66b76e0218cf
diff --git a/net/d80211/ieee80211.c b/net/d80211/ieee80211.c
index 542fec9..7ceef10 100644
--- a/net/d80211/ieee80211.c
+++ b/net/d80211/ieee80211.c
@@ -1339,7 +1339,6 @@ static void ieee80211_tx_pending(unsigne
int i, ret, reschedule = 0;
netif_tx_lock_bh(dev);
- dev->xmit_lock_owner = smp_processor_id();
for (i = 0; i < local->hw->queues; i++) {
if (__ieee80211_queue_stopped(local, i))
continue;
@@ -1364,7 +1363,6 @@ static void ieee80211_tx_pending(unsigne
reschedule = 1;
}
}
- dev->xmit_lock_owner = -1;
netif_tx_unlock_bh(dev);
if (reschedule)
netif_schedule(dev);
--
1.3.1
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-07-13 2:30 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
2006-07-13 2:30 ` John W. Linville [this message]
-- 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=20060713023017.GA16084@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.