From: Michael Buesch <mb@bu3sch.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
James Ketrenos <jketreno@linux.intel.com>
Subject: Re: cfg80211 wext compat w/o wext code changes, rtnl locking
Date: Fri, 30 Mar 2007 12:11:04 +0200 [thread overview]
Message-ID: <200703301211.05261.mb@bu3sch.de> (raw)
In-Reply-To: <1175122815.8807.21.camel@johannes.berg>
On Thursday 29 March 2007 01:00, Johannes Berg wrote:
> - if(handler != NULL) {
> + if (handler) {
> + if (!dev->wireless_handlers->no_locking)
> + rtnl_lock();
Is sparse OK with this conditional locking?
--
Greetings Michael.
next prev parent reply other threads:[~2007-03-30 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 23:00 cfg80211 wext compat w/o wext code changes, rtnl locking Johannes Berg
2007-03-30 10:11 ` Michael Buesch [this message]
2007-03-30 10:37 ` Johannes Berg
2007-04-02 18:00 ` Pavel Roskin
2007-04-02 18:15 ` Johannes Berg
2007-04-02 18:23 ` Pavel Roskin
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=200703301211.05261.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jketreno@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).