All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rfkill rewrite bug
Date: Mon, 20 Apr 2009 10:20:27 +0100	[thread overview]
Message-ID: <49EC3E5B.8060403@tuffmail.co.uk> (raw)
In-Reply-To: <1240217064.28218.0.camel@johannes.local>

Johannes Berg wrote:
> On Mon, 2009-04-20 at 09:33 +0100, Alan Jenkins wrote:
>
>   
>> Ok, revised patch is below. Don't forget the set_sw_state() ->
>> set_global_sw_state() change; I didn't include that.
>>     
>
> Ok, will do. Thanks for the patch, I'll integrate it into mine.
>
>   
>> Note that there other pending changes to the rfkill code in eeepc-laptop.
>>
>> "[PATCH] eee-laptop: Register as a pci-hotplug device"
>> <http://thread.gmane.org/gmane.linux.kernel/791730/focus=38724>
>>
>> "[PATCH] eeepc-laptop: Work around rfkill firmware bug"
>> <http://thread.gmane.org/gmane.linux.acpi.devel/38424>
>>
>> The second is mine; sorry for not warning about it sooner.  So you/we
>> probably need to co-ordinate with the maintainer.  I'd CC linux-acpi,
>> because that's where most platform driver changes are submitted.
>>     
>
> Ok, thanks for the heads up. Do you think this will generate significant
> conflicts?
>   

I'm not quite sure what would be considered significant, but it's not
trivial.  At a high level, I don't think the new behaviours conflict
with the new rfkill semantics :-).  But the firmware bug workaround
can't be resolved completely mechanically.  And the pci-hotplug patch
touches the rfkill error path.

  reply	other threads:[~2009-04-20  9:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08 13:37 [PATCH] rfkill: document removal of notifier chain Alan Jenkins
2009-04-08 15:21 ` Johannes Berg
2009-04-08 17:21   ` Alan Jenkins
2009-04-13 19:00     ` rfkill rewrite bug Alan Jenkins
2009-04-13 18:56       ` Johannes Berg
2009-04-14 20:46       ` Johannes Berg
2009-04-18  8:17         ` Alan Jenkins
2009-04-18  8:15           ` Johannes Berg
2009-04-18  8:28           ` Johannes Berg
2009-04-18  9:43             ` Alan Jenkins
2009-04-18 12:24               ` Johannes Berg
2009-04-18 13:29                 ` Rfkill rewrite: eeepc-laptop resume Alan Jenkins
2009-04-18 13:33                   ` Johannes Berg
2009-04-18 14:02                     ` Alan Jenkins
2009-04-18 14:10                       ` Johannes Berg
2009-04-18 15:49                 ` rfkill rewrite bug Alan Jenkins
2009-04-18 15:57                   ` Johannes Berg
2009-04-18 17:48                     ` Alan Jenkins
2009-04-18 17:57                       ` Johannes Berg
2009-04-18 18:03                         ` Alan Jenkins
2009-04-18 17:42                 ` Alan Jenkins
2009-04-18 17:59                   ` Johannes Berg
2009-04-20  8:33                     ` Alan Jenkins
2009-04-20  8:44                       ` Johannes Berg
2009-04-20  9:20                         ` Alan Jenkins [this message]
2009-04-20 11:28                           ` 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=49EC3E5B.8060403@tuffmail.co.uk \
    --to=alan-jenkins@tuffmail.co.uk \
    --cc=johannes@sipsolutions.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.