public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Marco Chiappero <marco@absence.it>
To: netdev@vger.kernel.org
Cc: johannes@sipsolutions.net
Subject: rfkill-input to be removed
Date: Thu, 21 Apr 2011 10:28:23 +0200	[thread overview]
Message-ID: <4DAFEAA7.5090003@absence.it> (raw)

While working on the the sony-laptop driver, adding support for 
persistent rfkill state storing and adding the SW_RFKILL_ALL switch 
event forwarding to the input core to notify userspace, I realized that 
rfkill-input interferes with correct behavior of the driver, vanishing 
the hardware device state storing. Then, looking at 
Documentation/feature-removal-schedule.txt I realized that rfkill-input 
was scheduled to be removed in 2.6.33, but it's still there in 2.6.39. 
Please remove that code as soon as possible, rfkill input events should 
be handled by user space tools.

             reply	other threads:[~2011-04-21  8:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21  8:28 Marco Chiappero [this message]
2011-04-21 13:47 ` rfkill-input to be removed Marco Chiappero
2011-04-21 15:51   ` Dan Williams
2011-04-21 16:22 ` Johannes Berg
2011-04-21 16:45   ` Marco Chiappero

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=4DAFEAA7.5090003@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