linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: rfkill rewrite bug
Date: Mon, 20 Apr 2009 10:44:24 +0200	[thread overview]
Message-ID: <1240217064.28218.0.camel@johannes.local> (raw)
In-Reply-To: <49EC3366.7080206@tuffmail.co.uk> (sfid-20090420_103348_397116_B4EBC1A4)

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

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?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <49DCA88E.6060400@tuffmail.co.uk>
     [not found] ` <1239204090.16477.1.camel@johannes.local>
     [not found]   ` <49DCDD2E.80705@tuffmail.co.uk>
     [not found]     ` <49E38BBC.5010708@tuffmail.co.uk>
     [not found]       ` <1239741968.4205.1.camel@johannes.local>
     [not found]         ` <49E98C86.2040308@tuffmail.co.uk>
     [not found]           ` <1240043283.5792.0.camel@johannes.local>
2009-04-18  9:43             ` rfkill rewrite bug 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 [this message]
2009-04-20  9:20                         ` Alan Jenkins
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=1240217064.28218.0.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=alan-jenkins@tuffmail.co.uk \
    --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;
as well as URLs for NNTP newsgroup(s).