All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: drago01 <drago01@gmail.com>
Cc: "Adel Gadllah" <adel.gadllah@gmail.com>,
	linux-wireless@vger.kernel.org, stefano.brivio@polimi.it,
	"Larry Finger" <larry.finger@lwfinger.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	"Henrique de Moraes Holschuh" <hmh@hmh.eng.br>,
	"Ivo van Doorn" <ivdoorn@gmail.com>
Subject: Re: [PATCH/RFC] b43: remove input device usage for rfkill
Date: Tue, 1 Jul 2008 12:38:18 +0200	[thread overview]
Message-ID: <200807011238.18600.mb@bu3sch.de> (raw)
In-Reply-To: <f6ca9fed0807010333s61d035e0m13e2d6b81ef63a9b@mail.gmail.com>

On Tuesday 01 July 2008 12:33:17 drago01 wrote:
> On Tue, Jul 1, 2008 at 12:27 PM, Michael Buesch <mb@bu3sch.de> wrote:
> > On Tuesday 01 July 2008 11:55:11 Adel Gadllah wrote:
> >> Hi,
> >> The attached patch removes the input device dependency and replaces
> >> the polldev by a timer.
> >> The timer polls the device and sets the rfkill state.
> >> I build tested the patch only because I don't have access to the
> >> hardware, hence the RFC.
> >> Can someone with the access to the hardware test and verify this?
> >> If it works I will submit a similar patch for b43legacy.
> >>
> >> -----------------------
> >> This patch removes the dependency on the input device and replaces the
> >> polldev with a timer for polling the rfkill state.
> >
> >
> > I'm pretty sure this will generate a lot of bugreports complaining that
> > rfkill silently broke, as the userspace is not setup correctly.
> 
> OK, so how to proceed? Just leave the input device?

No well. This probably is the right way to go. However I just wanted to
say that I'm pretty sure it will generate lots of bugreports that I
will ignore. ;)

But I am wondering _why_ we need to turn all this upside down.
What's so bad about having an input device in the kernel? What's the
advantage of having userspace do the work?

-- 
Greetings Michael.

  reply	other threads:[~2008-07-01 10:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-01  9:55 [PATCH/RFC] b43: remove input device usage for rfkill Adel Gadllah
2008-07-01  9:58 ` Johannes Berg
2008-07-01 10:05   ` [PATCH/RFC v2] " Adel Gadllah
2008-07-01 10:08     ` Johannes Berg
2008-07-01 10:19       ` [PATCH/RFC v3] " Adel Gadllah
2008-07-01 10:23         ` Johannes Berg
2008-07-01 10:31           ` drago01
2008-07-01 10:29         ` Michael Buesch
2008-07-01 10:34           ` drago01
2008-07-01 10:29         ` Ivo van Doorn
2008-07-01 10:27 ` [PATCH/RFC] " Michael Buesch
2008-07-01 10:33   ` drago01
2008-07-01 10:38     ` Michael Buesch [this message]
2008-07-01 14:34   ` Henrique de Moraes Holschuh
2008-07-01 14:38     ` Johannes Berg
2008-07-01 16:50       ` Henrique de Moraes Holschuh
2008-07-01 17:01         ` Johannes Berg
2008-07-01 17:14           ` Larry Finger
2008-07-01 17:35             ` Henrique de Moraes Holschuh
2008-07-01 18:21               ` Larry Finger
2008-07-01 21:20                 ` Dan Williams
2008-07-02  2:45                   ` Larry Finger
2008-07-01 17:33           ` Henrique de Moraes Holschuh
2008-07-01 18:01             ` Johannes Berg
2008-07-01 18:41               ` Henrique de Moraes Holschuh
2008-07-01 18:44                 ` Johannes Berg
2008-07-01 22:52                   ` Henrique de Moraes Holschuh
2008-07-01 22:56                     ` Johannes Berg
2008-07-01 23:57                       ` Henrique de Moraes Holschuh
2008-07-02  2:43                         ` Larry Finger
2008-07-02  7:21                         ` Johannes Berg
2008-07-02  7:31                           ` Johannes Berg
2008-07-02 16:02                             ` Henrique de Moraes Holschuh
2008-07-02 13:16                           ` Dmitry Torokhov

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=200807011238.18600.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=adel.gadllah@gmail.com \
    --cc=drago01@gmail.com \
    --cc=hmh@hmh.eng.br \
    --cc=ivdoorn@gmail.com \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=stefano.brivio@polimi.it \
    /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.