public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"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: Tue, 9 Jun 2009 18:21:12 +0900	[thread overview]
Message-ID: <20090609092112.GE7682@kamineko.org> (raw)
In-Reply-To: <4A2E1DE3.4020509@tuffmail.co.uk>

On Tue, Jun 09, 2009 at 09:31:31AM +0100, Alan Jenkins wrote:
> Mattia Dongili wrote:
>> On Mon, Jun 08, 2009 at 12:36:58PM +0200, Johannes Berg wrote:
>>   
>>> 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.
>>>     
>>
>> Just to confirm, is this patch going to sit in the wireless-testing tree
>> and you will submit it for inclusion together with the rfkill work
>> right?
>>   
>
> Yes.  I probably didn't need to ping you at this point.
>
> It just bothered me because I was effectively reverting a recent commit.  
> I figuired I should let you know.  In case it didn't work, when it was 
> merged you'd know why I did it and who to blame.  But there is always Git 
> history for that :-).

Errm... now that I look at that patch more closely, the code you're
modifying is not upstream either.
Anyway thanks for the ping, I'll take a look at what's going on in the
wireless-testing tree ;)

cheers
-- 
mattia
:wq!

  reply	other threads:[~2009-06-09  9:21 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
     [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 [this message]
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=20090609092112.GE7682@kamineko.org \
    --to=malattia@linux.it \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-wireless@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