From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <sourcejedi.lkml@googlemail.com>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Vivek Natarajan <Vivek.Natarajan@atheros.com>,
Easwar Krishnan <Easwar.Krishnan@atheros.com>,
Nataraj Sadasivam <Nataraj.Sadasivam@atheros.com>,
Kathir Ganapthy <Kathir.Ganapthy@atheros.com>,
Ponmudi Ramachandran <Ponmudi.Ramachandran@atheros.com>,
Senthilkumar Balasubramanian
<Senthilkumar.Balasubramanian@atheros.com>
Subject: Re: [RFT v9] rfkill: rewrite
Date: Thu, 14 May 2009 11:08:48 +0200 [thread overview]
Message-ID: <1242292128.10076.38.camel@johannes.local> (raw)
In-Reply-To: <9b2b86520905140202y539f8b93m9669e2c8c7ffbdcd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
On Thu, 2009-05-14 at 10:02 +0100, Alan Jenkins wrote:
> > I think my new 4 patches should address this and it'd be great to hear
> > your tests as you can reproduce easily. We are able to see something
> > like this but only after 3 hours of testing. Since it seems you might
> > be able to reproduce quickly it would help.
>
> Glad to be of service :-).
>
> I applied your four patches on top of my current tree
> (wireless-testing+rfkill rewrite), and it fixed the OOPS.
>
> As a sanity check, I tried un-applying patch 4/4 (cfg80211: fix race
> between core hint and driver's custom apply), since that looked like
> the fix I was interested in. Un-applying this fix caused the OOPS to
> reappear.
Very good, thank you! That means I don't have to fix anything in
rfkill :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-05-14 9:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 8:31 [RFT v9] rfkill: rewrite Johannes Berg
2009-05-12 14:09 ` Alan Jenkins
2009-05-13 10:49 ` Johannes Berg
2009-05-13 14:36 ` Alan Jenkins
2009-05-13 14:38 ` Johannes Berg
2009-05-13 21:48 ` Luis R. Rodriguez
2009-05-13 21:45 ` Luis R. Rodriguez
2009-05-14 9:02 ` Alan Jenkins
2009-05-14 9:08 ` Johannes Berg [this message]
2009-05-14 9:58 ` Alan Jenkins
2009-05-14 10:00 ` Johannes Berg
2009-05-14 4:34 ` Luis R. Rodriguez
2009-05-14 8:24 ` Alan Jenkins
2009-05-12 17:26 ` Will Keaney
2009-05-12 17:52 ` Johannes Berg
2009-05-12 17:59 ` Dan Williams
2009-05-12 18:04 ` Johannes Berg
2009-05-12 18:09 ` Will Keaney
2009-05-12 18:13 ` Johannes Berg
2009-05-13 21:40 ` Henrique de Moraes Holschuh
2009-05-13 22:19 ` Johannes Berg
2009-05-15 1:27 ` Henrique de Moraes Holschuh
2009-05-15 8:23 ` Johannes Berg
2009-05-18 11:00 ` Henrique de Moraes Holschuh
2009-05-19 12:12 ` Johannes Berg
2009-05-19 18:24 ` Henrique de Moraes Holschuh
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=1242292128.10076.38.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Easwar.Krishnan@atheros.com \
--cc=Kathir.Ganapthy@atheros.com \
--cc=Nataraj.Sadasivam@atheros.com \
--cc=Ponmudi.Ramachandran@atheros.com \
--cc=Senthilkumar.Balasubramanian@atheros.com \
--cc=Vivek.Natarajan@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=sourcejedi.lkml@googlemail.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 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.