From: Marco Chiappero <marco@absence.it>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org
Subject: Re: rfkill-input to be removed
Date: Thu, 21 Apr 2011 18:45:32 +0200 [thread overview]
Message-ID: <4DB05F2C.1080208@absence.it> (raw)
In-Reply-To: <1303402951.3597.27.camel@jlt3.sipsolutions.net>
Il 21/04/2011 18:22, Johannes Berg ha scritto:
> Yeah we noticed this before with some other drivers. The persistent
> stuff seems to only be suitable for a small number of semantics.
Sorry, what do you mean exactly? The persistent stuff seems to work well
with those notebooks.
> Frankly, I don't think we're ready for this yet, most distros don't yet
> ship the rfkill daemon.
Ok, in the meantime I'm going to avoid the SW_RFKILL_ALL switch event
forwarding, unless the master_switch_mode=1 is going to be changed to
honor the stored power state on drivers loading as well, not only when
moving the "kill all" switch (it seems that on boot every device is
always turned on, which is very annoying).
prev parent reply other threads:[~2011-04-21 16:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 8:28 rfkill-input to be removed Marco Chiappero
2011-04-21 13:47 ` Marco Chiappero
2011-04-21 15:51 ` Dan Williams
2011-04-21 16:22 ` Johannes Berg
2011-04-21 16:45 ` Marco Chiappero [this message]
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=4DB05F2C.1080208@absence.it \
--to=marco@absence.it \
--cc=johannes@sipsolutions.net \
--cc=netdev@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