From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: James Ketrenos <jketreno@linux.intel.com>,
linux-wireless@vger.kernel.org,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: "Stable" branch of mac80211
Date: Mon, 30 Apr 2007 14:45:58 -0400 [thread overview]
Message-ID: <20070430184558.GD5994@tuxdriver.com> (raw)
In-Reply-To: <20070430192951.26bdf1df@griffin.suse.cz>
On Mon, Apr 30, 2007 at 07:29:51PM +0200, Jiri Benc wrote:
> On Mon, 30 Apr 2007 09:52:51 -0700, James Ketrenos wrote:
> > I assume the entire new tree will be marked as 'experimental', so what
> > is the advantage gained by pulling this code out now?
>
> Once the code is in vanilla, user space interfaces are set in stone.
> Regarding .11n, untested and unreviewed patches shouldn't go to vanilla.
ACK
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-04-30 19:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 17:48 "Stable" branch of mac80211 Jiri Benc
2007-04-29 18:14 ` Michael Wu
2007-04-29 19:55 ` Jiri Benc
2007-04-30 16:52 ` James Ketrenos
2007-04-30 17:29 ` Jiri Benc
2007-04-30 18:45 ` John W. Linville [this message]
2007-05-01 1:00 ` Jiri Benc
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=20070430184558.GD5994@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=jketreno@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
/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