From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: wey-yi.w.guy@intel.com, linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] hw scan fixes
Date: Fri, 30 Jul 2010 13:30:45 +0200 [thread overview]
Message-ID: <20100730113045.923567583@sipsolutions.net> (raw)
I'm rolling these up because without the iwlwifi
fix I'm pretty sure we will also get lockdep
warnings even if the actual deadlock scenario
is rather unlikely to start with.
Technically these are 2.6.35 regressions, but
I guess it's a little late?
johannes
next reply other threads:[~2010-07-30 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 11:30 Johannes Berg [this message]
2010-07-30 11:30 ` [PATCH 1/2] iwlwifi: fix possible recursive locking deadlock Johannes Berg
2010-07-30 11:30 ` [PATCH 2/2] mac80211: fix scan locking wrt. hw scan Johannes Berg
2010-07-30 12:14 ` [PATCH 0/2] hw scan fixes Johannes Berg
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=20100730113045.923567583@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=wey-yi.w.guy@intel.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).