From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Colin Guthrie <gmane@colin.guthr.ie>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [Regression] Problem with rfkill on 2.6.38
Date: Mon, 9 May 2011 18:11:44 +0100 [thread overview]
Message-ID: <20110509171144.GA7194@srcf.ucam.org> (raw)
In-Reply-To: <4DC81FC7.9040503@colin.guthr.ie>
On Mon, May 09, 2011 at 06:09:27PM +0100, Colin Guthrie wrote:
> Just a quick (non-compile) followup from my last email... blacklisting
> the dell-laptop module works around the issue, so I think the commit
> previously mentioned is indeed the culprit (as it's the only recent
> commit and does fiddle with the rfkill stuff).
>
> Not sure what the best track forward is, but it's certainly a
> regression, so should probably be fixed or reverted until a more
> complete fix is found.
If you can confirm that with a build then I'll do that.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-05-09 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ip6j66$o5f$1@dough.gmane.org>
2011-05-09 8:36 ` [Regression] Problem with rfkill on 2.6.38 Johannes Berg
2011-05-09 16:30 ` Colin Guthrie
2011-05-09 17:09 ` Colin Guthrie
2011-05-09 17:11 ` Matthew Garrett [this message]
[not found] ` <20110509171144.GA7194-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2011-05-10 9:36 ` Colin Guthrie
[not found] ` <4DC9072D.4030103-D409yXkIzt2rnn0nCzrM/w@public.gmane.org>
2011-05-10 14:48 ` Keng-Yü Lin
[not found] ` <BANLkTinVwnSei_VobfKtgzrwSP+cJSvxaQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-10 15:12 ` Colin Guthrie
2011-06-24 10:54 ` Colin Guthrie
2011-06-24 12:29 ` Keng-Yü Lin
2011-06-24 13:23 ` John W. Linville
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=20110509171144.GA7194@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=gmane@colin.guthr.ie \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=platform-driver-x86@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