From: Pavel Roskin <proski@gnu.org>
To: Bob Copeland <me@bobcopeland.com>
Cc: ath5k-devel@lists.ath5k.org,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] ath5k: fix recursive locking in ath5k_beacon_update
Date: Fri, 18 Jul 2008 11:39:59 -0400 [thread overview]
Message-ID: <1216395599.18320.7.camel@dv> (raw)
In-Reply-To: <20080718134345.M6916@bobcopeland.com>
On Fri, 2008-07-18 at 09:50 -0400, Bob Copeland wrote:
> Hi all,
>
> I found a lockdep error while playing with AP mode on ath5k. I think
> this is triggerable today in ad-hoc mode.
I think it's a perfect candidate for 2.6.27. If it can affect actual
functionality, it should go to 2.6.26.1.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-07-18 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 13:50 [PATCH] ath5k: fix recursive locking in ath5k_beacon_update Bob Copeland
2008-07-18 15:39 ` Pavel Roskin [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=1216395599.18320.7.camel@dv \
--to=proski@gnu.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=me@bobcopeland.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