From: Kalle Valo <kalle.valo@iki.fi>
To: linville@tuxdriver.com
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: fix update_tkip_key() documentation about the context
Date: Sun, 24 Jan 2010 15:59:54 +0200 [thread overview]
Message-ID: <87wrz7ob6t.fsf@purkki.valot.fi> (raw)
In-Reply-To: <20100124125512.14746.63093.stgit@tikku> (Kalle Valo's message of "Sun\, 24 Jan 2010 14\:55\:12 +0200")
Kalle Valo <kalle.valo@iki.fi> writes:
> Johannes noticed that I had incorrectly documented the context of
> update_tkip_key() driver operation. It must be atomic because all
> RX code is run inside rcu critical section.
>
> Reported-by: Johannes Berg <johannes@sipsolutions.net>
> Signed-off-by: Kalle Valo <kalle.valo@iki.fi>
John, I forgot to mention that this might fix some false warnings
caused by my patch "mac80211: annotate sleeping driver ops". I haven't
seen any reports, yet. Forturnately the patch is not in 2.6.33 AFAIK.
--
Kalle Valo
prev parent reply other threads:[~2010-01-24 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 12:55 [PATCH] mac80211: fix update_tkip_key() documentation about the context Kalle Valo
2010-01-24 13:59 ` Kalle Valo [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=87wrz7ob6t.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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