From: Bob Copeland <me@bobcopeland.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath5k-devel@lists.ath5k.org
Subject: Re: lockdep spew
Date: Sat, 20 Jun 2009 12:12:17 -0400 [thread overview]
Message-ID: <20090620161217.GA26000@hash.localnet> (raw)
In-Reply-To: <1245412823.16399.18.camel@johannes.local>
On Fri, Jun 19, 2009 at 02:00:23PM +0200, Johannes Berg wrote:
> > [ 966.937836] ======================================================
> > [ 966.937855] [ INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected ]
> > [ 966.937863] 2.6.30-wl #136
> > [ 966.937869] ------------------------------------------------------
>
> I think this will be fixed by the local_bh_disable patch I posted
> recently.
This one?
commit 38d64294a1116bef7cde45eef3a4554d6d628123
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Thu Jun 18 17:25:11 2009 +0200
mac80211: fix ieee80211_xmit call context
Hmm, I still have it with that.
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-06-20 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 11:30 lockdep spew Bob Copeland
2009-06-19 12:00 ` Johannes Berg
2009-06-20 16:12 ` Bob Copeland [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=20090620161217.GA26000@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--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).