linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: joe@nahmias.net (Joseph Nahmias)
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	562016-quiet@bugs.debian.org
Subject: Re: [RFC/T] cfg80211: fix race between deauth and assoc response
Date: Wed, 23 Dec 2009 16:21:11 +0000	[thread overview]
Message-ID: <20091223162111.GA902@nahmias.net> (raw)
In-Reply-To: <1261481565.22748.40.camel@johannes.local>

On Tue, Dec 22, 2009 at 12:32:45PM +0100, Johannes Berg wrote:
> I don't suppose you have a way of reproducing this issue? I know this
> patch will remove the warning, and I'm pretty sure it's correct too, but
> I can't really test this scenario.

Sorry, I've tried, but I cannot reproduce.

--Joe

  reply	other threads:[~2009-12-23 16:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 11:32 [RFC/T] cfg80211: fix race between deauth and assoc response Johannes Berg
2009-12-23 16:21 ` Joseph Nahmias [this message]
2009-12-23 16:25   ` 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=20091223162111.GA902@nahmias.net \
    --to=joe@nahmias.net \
    --cc=562016-quiet@bugs.debian.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).