From: Colin Guthrie <gmane@colin.guthr.ie>
To: "Keng-Yü Lin" <keng-yu.lin@canonical.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
platform-driver-x86@vger.kernel.org,
Thomas Backlund <tmb@mageia.org>
Subject: Re: [Regression] Problem with rfkill on 2.6.38
Date: Fri, 24 Jun 2011 11:54:13 +0100 [thread overview]
Message-ID: <4E046CD5.2070709@colin.guthr.ie> (raw)
In-Reply-To: <BANLkTinVwnSei_VobfKtgzrwSP+cJSvxaQ@mail.gmail.com>
'Twas brillig, and Keng-Yü Lin at 10/05/11 15:48 did gyre and gimble:
> On Tue, May 10, 2011 at 11:36 AM, Colin Guthrie <mageia@colin.guthr.ie> wrote:
>> 'Twas brillig, and Matthew Garrett at 09/05/11 18:11 did gyre and gimble:
>>> 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.
>>
>> ACK. Reverting that commit and unblacklisting the dell_laptop module
>> restores the previous, working functionality. I've flipped rfkill a few
>> times and it's always worked fine.
Just wondering if there was any progress on this. I ACKed a regression
but it was not reverted.... I thought the standard practice was to
revert until a fuller fix was found.
I appreciate some other users will not get their fix but I was still
under the impression that this was the policy?
I don't see any relevant changes in the 2.6.39 kernel:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.39.y.git;a=history;f=drivers/platform/x86/dell-laptop.c;h=de301aa8e5c3799620ff5a06372b5e1942c2dab2;hb=HEAD
nor in Linus' 2.6 tree (which I presume is actually for 3.0 these days?):
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/platform/x86/dell-laptop.c;h=d3841de6a8cf199ec08b24bd85f50a0af0490d37;hb=HEAD
> May I have the model of your Dell laptop?
snip....
I supplied all this info before here:
http://thread.gmane.org/gmane.linux.kernel.wireless.general/68758
Anything else I can do to move this forward?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mageia Contributor [http://www.mageia.org/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
next prev parent reply other threads:[~2011-06-24 11:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 14:00 [Regression] Problem with rfkill on 2.6.38 Colin Guthrie
2011-04-28 11:40 ` Stanislaw Gruszka
2011-05-09 8:36 ` Johannes Berg
2011-05-09 16:30 ` Colin Guthrie
2011-05-09 17:09 ` Colin Guthrie
2011-05-09 17:11 ` Matthew Garrett
2011-05-10 9:36 ` Colin Guthrie
2011-05-10 14:48 ` Keng-Yü Lin
2011-05-10 15:12 ` Colin Guthrie
2011-06-24 10:54 ` Colin Guthrie [this message]
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=4E046CD5.2070709@colin.guthr.ie \
--to=gmane@colin.guthr.ie \
--cc=johannes@sipsolutions.net \
--cc=keng-yu.lin@canonical.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tmb@mageia.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).