public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: rfkill-input madness
Date: Mon, 30 Mar 2009 10:23:44 -0300	[thread overview]
Message-ID: <20090330132344.GA11934@khazad-dum.debian.net> (raw)
In-Reply-To: <1238262651.4217.21.camel@johannes.local>

On Sat, 28 Mar 2009, Johannes Berg wrote:
> Ok so you want to add "global" states mostly -- that's fine, but not all
> that useful since userspace cannot really claim globally. I also don't
> see a point -- if userspace wanted to do global stuff it might just as
> well do nothing.

The point of doing global stuff is to do rfkill-input in userspace, the way
userspace might want to do it.

Without the global state being exposed, userspace really can't do anything
properly, and rfkill-input is needed for any semblance of good rfkill input
event handling.

I can't say I strongly want it, since I am happy enough with rfkill-input,
though.  But the API to userspace _is_ incomplete if the global states and
global functionality are not exposed.

-- 
  "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

  reply	other threads:[~2009-03-30 13:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 13:06 rfkill-input madness Johannes Berg
2009-03-27 14:30 ` Henrique de Moraes Holschuh
2009-03-27 21:10   ` Johannes Berg
2009-03-28  0:52     ` Henrique de Moraes Holschuh
2009-03-28 17:50       ` Johannes Berg
2009-03-30 13:23         ` Henrique de Moraes Holschuh [this message]
2009-03-30 14:11           ` Johannes Berg
2009-03-30 17:21             ` Henrique de Moraes Holschuh
2009-03-30 17:29               ` 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=20090330132344.GA11934@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --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