From: Larry Finger <Larry.Finger@lwfinger.net>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Michael Buesch <mb@bu3sch.de>,
Adel Gadllah <adel.gadllah@gmail.com>,
linux-wireless@vger.kernel.org, stefano.brivio@polimi.it,
"John W. Linville" <linville@tuxdriver.com>,
Ivo van Doorn <ivdoorn@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Subject: Re: [PATCH/RFC] b43: remove input device usage for rfkill
Date: Tue, 01 Jul 2008 21:43:16 -0500 [thread overview]
Message-ID: <486AEB44.9030704@lwfinger.net> (raw)
In-Reply-To: <20080701235747.GG4292@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
> On Wed, 02 Jul 2008, Johannes Berg wrote:
> I apologise. Re-reading it, it does look like a rant, indeed. It wasn't
> supposed to be, but the tone came up nasty and quite defensive. I didn't
> intend it to.
>
> The sheer ammount of explanations I have had to type over the whole rfkill
> business is, apparently, getting to me a lot more than expected, and I guess
> that put me in the defensive. There is no excuse for that.
>
> So, please accept my appologies on the tone of the last email. Please
> reconsider reading that email in full, and please try to ignore the rantness
> smell in it. I did try to explain the technical reasons why some changes
> would be needed in b43.
>
> I am sorry I didn't send you any patches. I don't have any access to a b43
> device, and as a rule, I try to avoid modifying code I will not be able to
> test, especially when I don't know the code to begin with and the changes
> are not going to be small, obvious ones.
>
>> To address one point though: userspace does want a notification when the
>> hw-rfkill is activated so it (e.g. network manager) can ask people to
>> un-rfkill their device.
>
> I tried to add such notifications directly to the rfkill class. rfkill now
> issues uevents and calls a notification chain for any state changes. It has
> been modified to differentiate hw-rfkill from sw-rfkill, and export that
> information to userspace for network-manager and other applications to use.
I am more than happy to test any b43 patches that you generate. My b43
device has a wireless switch.
Larry
next prev parent reply other threads:[~2008-07-02 2:41 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
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 [this message]
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=486AEB44.9030704@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=adel.gadllah@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--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 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).