From: Luciano Coelho <coelho@ti.com>
To: Arik Nemtsov <arik@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: wl12xx compat wireless rcu_read_lock issue
Date: Tue, 11 Jan 2011 18:59:35 +0200 [thread overview]
Message-ID: <1294765175.1981.4.camel@pimenta> (raw)
In-Reply-To: <AANLkTi=4H6TXvXWi_KVBEn3G_aNW_8qZfBF7g36WRED6@mail.gmail.com>
On Tue, 2011-01-11 at 17:03 +0100, Arik Nemtsov wrote:
> On Tue, Jan 11, 2011 at 13:28, Luciano Coelho <coelho@ti.com> wrote:
> > I hadn't seen it before, but then again, I just integrated the AP
> > patches which added this code. The code has been tested quite well
> > before, but indeed this is broken.
[...]
> Actually this change is part of the HT patch series (in patch
> 18357850b694ba3fa29363c7d86ccd8783f4a065) so it was there quite some
> time.
> But I did port over without noticing the bug :)
Right, I didn't check very carefully when the bug was introduced and it
doesn't matter much anyway. But it's a bug and needs to be fixed. Does
any volunteers to send a patch or should I do it myself? (feeling
lazy :P)
--
Cheers,
Luca.
next prev parent reply other threads:[~2011-01-11 16:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 13:42 [PATCH 0/2] wl12xx: BA Initiator & receiver support Shahar Levi
2011-01-03 13:42 ` [PATCH v5 1/2] wl12xx: BA initiator support Shahar Levi
2011-01-10 15:00 ` Luciano Coelho
[not found] ` <AANLkTi=KnSjVVCN=9=PaL9_GYpDOpJFvD-LGxFXEevhw@mail.gmail.com>
2011-01-11 0:18 ` Levi, Shahar
2011-01-11 8:04 ` Luciano Coelho
2011-01-16 9:12 ` Levi, Shahar
2011-01-11 10:22 ` wl12xx compat wireless rcu_read_lock issue DE CESCO, Jonathan
2011-01-11 11:28 ` Luciano Coelho
[not found] ` <AANLkTi=4H6TXvXWi_KVBEn3G_aNW_8qZfBF7g36WRED6@mail.gmail.com>
2011-01-11 16:59 ` Luciano Coelho [this message]
2011-01-03 13:42 ` [PATCH v3 2/2] wl12xx: BA receiver support Shahar Levi
2011-01-10 15:44 ` Luciano Coelho
2011-01-11 0:54 ` Levi, Shahar
2011-01-16 13:38 ` Levi, Shahar
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=1294765175.1981.4.camel@pimenta \
--to=coelho@ti.com \
--cc=arik@wizery.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.