From: Pavel Roskin <proski@gnu.org>
To: Dan Williams <dcbw@redhat.com>
Cc: Jiri Benc <jbenc@suse.cz>,
Linux Wireless <linux-wireless@vger.kernel.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: mark as experimental
Date: Tue, 01 May 2007 13:12:48 -0400 [thread overview]
Message-ID: <1178039568.11535.7.camel@dv> (raw)
In-Reply-To: <1178020272.21671.1.camel@localhost.localdomain>
On Tue, 2007-05-01 at 07:51 -0400, Dan Williams wrote:
> On Mon, 2007-04-30 at 17:48 -0400, Pavel Roskin wrote:
> > On Mon, 2007-04-30 at 20:17 +0200, Jiri Benc wrote:
> > > Make the stack depend on EXPERIMENTAL. Also, change the name from "dscape"
> > > to "mac80211".
> >
> > Why is it needed to make mac80211 EXPERIMENTAL? With mac80211 already
> > in Ubuntu 7.04 and in the forthcoming Fedora 7, it must have received
> > more testing than some drivers not marked as EXPERIMENTAL.
>
> It's still just not there yet, especially WRT compatibility behavior for
> WEXT. I don't know if that justifies EXPERIMENTAL status, but most
> drivers don't appear to be production ready, from user reports.
That's my whole point. Mark the drivers experimental, not the common
code.
I think the issues affecting WEXT in non-mac80211 drivers by cfg80211
were fixed in December or so.
But anyway, it's better to have "experimental" mac80211 in the kernel
than no mac80211 at all.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-05-01 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 18:17 [PATCH] mac80211: mark as experimental Jiri Benc
2007-04-30 21:48 ` Pavel Roskin
2007-05-01 11:51 ` Dan Williams
2007-05-01 17:12 ` Pavel Roskin [this message]
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=1178039568.11535.7.camel@dv \
--to=proski@gnu.org \
--cc=dcbw@redhat.com \
--cc=jbenc@suse.cz \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).