From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [RFC] rfkill/rfkill-input userspace API
Date: Sat, 28 Mar 2009 09:37:59 -0300 [thread overview]
Message-ID: <20090328123759.GE7439@khazad-dum.debian.net> (raw)
In-Reply-To: <1238189689.4452.26.camel@johannes.local>
On Fri, 27 Mar 2009, Johannes Berg wrote:
> Can we do it after I rewrite the core to be useful wrt. hard/soft
> blocks? Same comments as in my other email apply. I'm sorry to waste
As long as you let me take a serious look on the new code, to make
sure the platform driver side is well represented, I don't see a
problem.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2009-03-28 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 15:58 [RFC] rfkill/rfkill-input userspace API Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 1/4] rfkill: prepare to export global states to userspace Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 2/4] rfkill: expose global switches through sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 3/4] rfkill: expose global state to sysfs Henrique de Moraes Holschuh
2009-03-27 15:58 ` [PATCH 4/4] rfkill: export events for global state changes Henrique de Moraes Holschuh
2009-03-27 21:34 ` [RFC] rfkill/rfkill-input userspace API Johannes Berg
2009-03-28 12:37 ` Henrique de Moraes Holschuh [this message]
2009-03-27 22:11 ` Matthew Garrett
2009-03-28 12:36 ` Henrique de Moraes Holschuh
2009-03-28 12:44 ` Matthew Garrett
2009-03-28 12:47 ` Henrique de Moraes Holschuh
2009-03-28 12:53 ` Matthew Garrett
2009-03-28 14:48 ` Henrique de Moraes Holschuh
2009-03-28 15:02 ` Matthew Garrett
2009-03-28 15:14 ` Henrique de Moraes Holschuh
2009-03-28 15:22 ` Matthew Garrett
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=20090328123759.GE7439@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--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 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).