From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Mattia Dongili <malattia@linux.it>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
linux acpi <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] sony-laptop: no need to unblock rfkill on load
Date: Mon, 08 Jun 2009 12:36:58 +0200 [thread overview]
Message-ID: <1244457418.18863.8.camel@johannes.local> (raw)
In-Reply-To: <4A2CE86F.9040209@tuffmail.co.uk>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Mon, 2009-06-08 at 11:31 +0100, Alan Jenkins wrote:
> The re-written rfkill core ensures rfkill devices are initialized to
> the system default state. The core calls set_block after registration
> so the driver shouldn't need to.
>
> Signed-off-by: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Good catch, thanks.
> ---
>
> This patch applies on top of the rfkill rewrite in the wireless-testing tree.
>
> diff --git a/drivers/platform/x86/sony-laptop.c b/drivers/platform/x86/sony-laptop.c
> index aec0b27..c1b21a4 100644
> --- a/drivers/platform/x86/sony-laptop.c
> +++ b/drivers/platform/x86/sony-laptop.c
> @@ -1114,7 +1114,6 @@ static int sony_nc_setup_rfkill(struct acpi_device *device,
> return err;
> }
> sony_rfkill_devices[nc_type] = rfk;
> - sony_nc_rfkill_set((void *)nc_type, false);
> return err;
> }
>
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-06-08 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 10:31 [PATCH] sony-laptop: no need to unblock rfkill on load Alan Jenkins
2009-06-08 10:36 ` Johannes Berg [this message]
[not found] ` <1244457418.18863.8.camel-YfaajirXv2244ywRPIzf9A@public.gmane.org>
2009-06-08 22:49 ` Mattia Dongili
[not found] ` <20090608224915.GA4583-pM3i+3kAS8Rg9hUCZPvPmw@public.gmane.org>
2009-06-09 8:31 ` Alan Jenkins
2009-06-09 9:21 ` Mattia Dongili
2009-06-09 9:30 ` Johannes Berg
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=1244457418.18863.8.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=malattia@linux.it \
/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