From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Lockdep complaint between drv->mtx and cfg80211_mutex
Date: Tue, 24 Mar 2009 09:21:28 +0100 [thread overview]
Message-ID: <1237882888.6278.2.camel@johannes.local> (raw)
In-Reply-To: <20090324004716.GA22925@tesla>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
On Mon, 2009-03-23 at 17:47 -0700, Luis R. Rodriguez wrote:
> What I had done was load mac80211_hwsim with the module parameters regtest=4 radios=2.
> Then I spawn hostapd for wlan0, bring up wlan1, trigger a scan using iw, and then
> I rename wlan1.
No need to do anything that complicated, the rename alone triggers it :)
I'm testing a patch, will send after that.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-03-24 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 0:47 Lockdep complaint between drv->mtx and cfg80211_mutex Luis R. Rodriguez
2009-03-24 8:21 ` Johannes Berg [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=1237882888.6278.2.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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).