linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Jiri Benc <jbenc@suse.cz>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] mac80211: mark as experimental
Date: Mon, 30 Apr 2007 17:48:43 -0400	[thread overview]
Message-ID: <1177969723.26986.30.camel@dv> (raw)
In-Reply-To: <20070430201742.1f53aa40@griffin.suse.cz>

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.

I don't think enabling mac80211 per se would destabilize the kernel.
Individual drivers could be marked experimental.  In particular,
bcm43xx_mac80211 needs such designation, since the softmac version is
much better currently.

If we encourage enabling mac80211, it would make it easier for the users
to compile and test mac80211 based drivers, such as iwlwifi.  Even
bcm43xx_mac80211 could be packaged separately to allow compilation
against an existing kernel for the users who want to test it without
upgrading the kernel.

In my opinion, marking mac80211 as EXPERIMENTAL would hinder testing of
mac80211 drivers without having any positive effect on the users who
want stability.

-- 
Regards,
Pavel Roskin


  reply	other threads:[~2007-04-30 21:48 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 [this message]
2007-05-01 11:51   ` Dan Williams
2007-05-01 17:12     ` Pavel Roskin

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=1177969723.26986.30.camel@dv \
    --to=proski@gnu.org \
    --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).