From: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Hin-Tak Leung <hintak.leung@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: hal, rfkill and compat-wireless (Re: [RFC/RFT] rtl8187: Implement rfkill support)
Date: Mon, 31 Aug 2009 13:13:20 -0700 [thread overview]
Message-ID: <1251749600.5165.1.camel@localhost.localdomain> (raw)
In-Reply-To: <43e72e890908311225r3b0d80bcqcb3e3e11d81a255e@mail.gmail.com>
On Mon, 2009-08-31 at 13:25 -0600, Luis R. Rodriguez wrote:
> OK not so bad except for:
>
> > kernel/net/wimax/wimax.ko
>
> That's touching another subsystem but we could technically merge wimax
> into compat-wireless if Inaky thinks that's a good idea. the point
> here is to unify anything that uses rfkill for backport usage.
Oh boy, can of worms
I have my own compat-wimax already, which already handles things for
backwards compat (many #ifdef hacks to simplify life) and which is
heavily used internally.
I don't really know how much worth it might be and I know I don't have
resources to support both.
> > If everything that depends on rkill is bundled with
> > compat-wireless, there is probablt no need for the symbol and sysfs
> > renaming hacks.
>
> Right which is why I think this may be reasonable to do. Any thoughts Inaky?
> Luis
--
-- Inaky
next prev parent reply other threads:[~2009-08-31 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 22:11 hal, rfkill and compat-wireless (Re: [RFC/RFT] rtl8187: Implement rfkill support) Hin-Tak Leung
2009-08-26 22:28 ` Luis R. Rodriguez
2009-08-26 22:55 ` Hin-Tak Leung
2009-08-26 23:45 ` Luis R. Rodriguez
2009-08-27 0:16 ` Hin-Tak Leung
2009-08-27 7:14 ` Johannes Berg
2009-08-27 9:43 ` Hin-Tak Leung
2009-08-31 18:43 ` Hin-Tak Leung
2009-08-31 18:54 ` Luis R. Rodriguez
[not found] ` <3ace41890908311215u378951e8j3283037ec6794764@mail.gmail.com>
2009-08-31 19:25 ` Luis R. Rodriguez
2009-08-31 20:13 ` Inaky Perez-Gonzalez [this message]
2009-08-31 20:40 ` Marcel Holtmann
2009-08-31 21:45 ` Luis R. Rodriguez
2009-08-31 23:05 ` Luis R. Rodriguez
2009-08-31 23:10 ` Inaky Perez-Gonzalez
2009-08-31 23:34 ` Luis R. Rodriguez
2009-09-01 0:09 ` Inaky Perez-Gonzalez
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=1251749600.5165.1.camel@localhost.localdomain \
--to=inaky.perez-gonzalez@intel.com \
--cc=hintak.leung@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/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).