From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: David Shwatrz <dshwatrz@gmail.com>,
Ivo van Doorn <ivdoorn@gmail.com>,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: Where is allow-ap-vlan-modes.patch ?
Date: Mon, 10 Nov 2008 09:28:07 -0500 [thread overview]
Message-ID: <20081110142806.GG3546@tuxdriver.com> (raw)
In-Reply-To: <874p2g0x9d.fsf@nokia.com>
On Mon, Nov 10, 2008 at 11:02:22AM +0200, Kalle Valo wrote:
> David Shwatrz <dshwatrz@gmail.com> writes:
>
> > In this occasion may I ask - what is the wireless-testing git tree?
> > is it based on wireless-next-2.6 or on wireless-2.6 tree?
>
> It's based on Linus' rc releases and has all the wireless patches
> which have been under development. I think John cherry picks the
> patches from wireless-testing to wireless-2.6 or wireless-next-2.6. So
> wireless-testing contains the bleeding edge wireless patches and if
> John thinks they are good enough, he submits them forward.
>
> Please correct me if I have understood something wrong.
That is basically right.
In the past patches often went to wireless-testing and to
wireless-next-2.6/wireless-2.6 at the about the same time. However
upstream standards have tightened in ways that make me feel it is
appropriate to give patches more public testing even before sending
them for -next.
In this case, I was also sick all last week which has slowed thing
a bit more...
Thanks,
John
--
John W. Linville Linux should be at the core
linville@tuxdriver.com of your literate lifestyle.
next prev parent reply other threads:[~2008-11-10 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 15:01 Where is allow-ap-vlan-modes.patch ? David Shwatrz
2008-11-09 15:04 ` Ivo van Doorn
2008-11-09 15:16 ` Kalle Valo
2008-11-10 8:48 ` David Shwatrz
2008-11-10 9:02 ` Kalle Valo
2008-11-10 14:28 ` John W. Linville [this message]
2008-11-10 15:42 ` David Shwatrz
2008-11-10 16:04 ` John W. Linville
2008-11-10 18:54 ` Stefanik Gábor
2008-11-10 19:00 ` Luis R. Rodriguez
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=20081110142806.GG3546@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dshwatrz@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.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;
as well as URLs for NNTP newsgroup(s).