From: Jiri Slaby <jirislaby@gmail.com>
To: Woody Suwalski <terraluna977@gmail.com>
Cc: Corentin Chary <corentin.chary@gmail.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Jiri Slaby <jslaby@suse.cz>,
acpi4asus-user@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: [ping] Re: eeepc: rfkill on 900A defunct
Date: Tue, 19 Apr 2011 15:53:51 +0200 [thread overview]
Message-ID: <4DAD93EF.3090205@gmail.com> (raw)
In-Reply-To: <4D777796.9030608@gmail.com>
On 03/09/2011 01:50 PM, Woody Suwalski wrote:
> Jiri Slaby wrote:
>> On 03/08/2011 11:22 AM, Corentin Chary wrote:
>>
>>> On Tue, Mar 8, 2011 at 10:06 AM, Jiri Slaby<jirislaby@gmail.com> wrote:
>>>
>>>> On 02/28/2011 10:49 AM, Jiri Slaby wrote:
>>>>
>>>>> On 11/24/2010 09:18 PM, Matthew Garrett wrote:
>>>>>
>>>>>> Hm. As a shorter term fix, can you try this (entirely untested!)
>>>>>> approach?
>>>>>>
>>>>> What is the status of this? Was there any alternative merged?
>>>>>
>>>> Ping.
>>>>
>>> Because this is Matthew's patch, and I have no hardware to test that
>>> patch, I'm not touching it.
>>>
>>> Jiri, on what models was this patch tested (only got 701 and 901 here) ?
>>>
>> It was 900A.
>>
>> thanks,
>>
> I have tested it on 900A and it does the trick.
> wlan can now be turned off/on (did not notice the problem before Jiri
> posted the patch ;-) ). So it should go in...
Any updates? Matthew?
--
js
prev parent reply other threads:[~2011-04-19 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 14:53 eeepc: rfkill on 900A defunct Jiri Slaby
2010-11-24 14:57 ` Matthew Garrett
2010-11-24 20:18 ` Matthew Garrett
2010-11-26 13:01 ` Woody Suwalski
2010-12-13 10:19 ` Jiri Slaby
2011-02-28 9:49 ` Jiri Slaby
2011-03-08 10:06 ` Jiri Slaby
2011-03-08 10:22 ` Corentin Chary
2011-03-08 10:51 ` Jiri Slaby
2011-03-09 12:50 ` Woody Suwalski
2011-04-19 13:53 ` Jiri Slaby [this message]
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=4DAD93EF.3090205@gmail.com \
--to=jirislaby@gmail.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=terraluna977@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox