From: Zhu Yi <yi.zhu@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Samuel Ortiz <sameo@linux.intel.com>
Subject: Re: [PATCH] cfg80211: mark all WEXT handlers _GPL
Date: Tue, 21 Apr 2009 16:31:54 +0800 [thread overview]
Message-ID: <1240302714.354.130.camel@debian> (raw)
In-Reply-To: <1240302453.17388.5.camel@johannes.local>
On Tue, 2009-04-21 at 16:27 +0800, Johannes Berg wrote:
> On Tue, 2009-04-21 at 09:08 +0800, Zhu Yi wrote:
> > On Tue, 2009-04-21 at 00:49 +0800, Johannes Berg wrote:
> > > The fact that these are exported is a technical detail
> > > of the conversion period -- we don't want anybody to
> > > start relying on these. Ultimately we want things to
> > > use cfg80211 only, and once everything that is in wext
> > > is converted to cfg80211 drivers will not need to touch
> > > wext _at all_.
> >
> > Johannes, why don't you want them to be used by others, say some fullmac
> > drivers? These functions can be used as glue from wext to cfg80211 in
> > the conversion period. After cfg80211 is ultimately used, they can be
> > removed all together of course.
>
> I don't expect any binary drivers to start using them anyway, but on the
> odd chance that somebody was considering that ... I just don't want any
> arguments at the conversion point that "we still need these symbols
> because we released a driver that uses them" which would mean we
> couldn't actually convert properly.
Fair enough, no binary drivers. I don't have any problem with your
patch. Just the comment "we don't want anybody to start relying on
these" makes me confuse.
Thanks,
-yi
next prev parent reply other threads:[~2009-04-21 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 16:49 [PATCH] cfg80211: mark all WEXT handlers _GPL Johannes Berg
2009-04-21 1:08 ` Zhu Yi
2009-04-21 8:27 ` Johannes Berg
2009-04-21 8:31 ` Zhu Yi [this message]
2009-04-21 8:57 ` Johannes Berg
2009-04-21 8:33 ` 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=1240302714.354.130.camel@debian \
--to=yi.zhu@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sameo@linux.intel.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).