All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Dan Williams <dcbw@redhat.com>, Will Keaney <keaneyw@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT v9] rfkill: rewrite
Date: Fri, 15 May 2009 10:23:08 +0200	[thread overview]
Message-ID: <1242375788.5799.40.camel@johannes.local> (raw)
In-Reply-To: <20090515012710.GC21718@khazad-dum.debian.net>

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

On Thu, 2009-05-14 at 22:27 -0300, Henrique de Moraes Holschuh wrote:
> On Thu, 14 May 2009, Johannes Berg wrote:
> > > As for the issue Dan reported, I have _no_ _idea_ of what it might be
> > > causing it, and a bissect would help wonders.  It will have to be fixed
> > > anyway (even if it is also fixed by the rfkill rewrite) if it is hosing
> > > 2.6.30 :-(
> > 
> > Dan? Now I'm confused? You mean Will's issue? Does thinkpad do LED
> 
> Probably.
> 
> > stuff? That's the only thing we changed recently in the current rfkill
> 
> Yes, thinkpad does LED stuff... but not on the rfkill path I think.
> Although one could certainly use a rfkill trigger on one of the thinkpad
> leds, and that would tie the two together...

Exactly. But for some reason I fail to comprehend rfkill had LED
triggers but never actually used them until Larry very recently added
that.

johannes

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

  reply	other threads:[~2009-05-15  8:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11  8:31 [RFT v9] rfkill: rewrite Johannes Berg
2009-05-12 14:09 ` Alan Jenkins
2009-05-13 10:49   ` Johannes Berg
2009-05-13 14:36     ` Alan Jenkins
2009-05-13 14:38       ` Johannes Berg
2009-05-13 21:48         ` Luis R. Rodriguez
2009-05-13 21:45   ` Luis R. Rodriguez
2009-05-14  9:02     ` Alan Jenkins
2009-05-14  9:08       ` Johannes Berg
2009-05-14  9:58         ` Alan Jenkins
2009-05-14 10:00           ` Johannes Berg
2009-05-14  4:34   ` Luis R. Rodriguez
2009-05-14  8:24     ` Alan Jenkins
2009-05-12 17:26 ` Will Keaney
2009-05-12 17:52   ` Johannes Berg
2009-05-12 17:59   ` Dan Williams
2009-05-12 18:04     ` Johannes Berg
2009-05-12 18:09       ` Will Keaney
2009-05-12 18:13         ` Johannes Berg
2009-05-13 21:40       ` Henrique de Moraes Holschuh
2009-05-13 22:19         ` Johannes Berg
2009-05-15  1:27           ` Henrique de Moraes Holschuh
2009-05-15  8:23             ` Johannes Berg [this message]
2009-05-18 11:00         ` Henrique de Moraes Holschuh
2009-05-19 12:12           ` Johannes Berg
2009-05-19 18:24             ` Henrique de Moraes Holschuh

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=1242375788.5799.40.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=dcbw@redhat.com \
    --cc=hmh@hmh.eng.br \
    --cc=keaneyw@gmail.com \
    --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.