All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 802.11 development process - extended documentation
Date: Mon, 1 Mar 2010 14:57:57 -0500	[thread overview]
Message-ID: <20100301195756.GF2961@tuxdriver.com> (raw)
In-Reply-To: <43e72e891002241618w10d5c45ar9303f074d0228217@mail.gmail.com>

On Wed, Feb 24, 2010 at 04:18:08PM -0800, Luis R. Rodriguez wrote:
> I've extended our 802.11 development process into a new section on our
> 802.11 wiki. I often get asked how this works from different parts of
> the company here at Atheros so figured it'd be easier to illustrate
> this as best as possible and share it.
> 
> http://wireless.kernel.org/en/developers/process
> 
> Hope it does justice, John if you see any mistakes feel free to edit.
> If the diagram seems fishy let me know what I can fix.

Overall, looks good.  I would make these changes to the diagram:

	-- remove wireless-testing -> wireless-next-2.6 arrow

	-- add me -> wireless-next-2.6 arrow

	-- add wireless-2.6 -> wireless-testing arrow

	-- add wireless-next-2.6 -> wireless-testing arrow

This would reflect that patches go into wireless-2.6 and
wireless-next-2.6, then are pulled to wireless-testing.  A few patches
may go to wireless-testing directly, but they will eventually be
reverted and possibly replaced with a patch in one of the other trees
(and subsequently pulled back into wireless-testing).  Nothing pulls
from wireless-testing (except developers).

Thanks for the doc! :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  parent reply	other threads:[~2010-03-01 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25  0:18 802.11 development process - extended documentation Luis R. Rodriguez
2010-02-25  0:34 ` Benoit PAPILLAULT
2010-02-25  0:43   ` Luis R. Rodriguez
2010-02-25  1:05     ` Luis R. Rodriguez
2010-02-25  2:34       ` Benoit PAPILLAULT
2010-02-25  2:37         ` Stephen Hemminger
2010-02-25  5:11           ` Luis R. Rodriguez
2010-02-25  4:53 ` Jaswinder Singh Rajput
2010-02-25  5:19   ` Luis R. Rodriguez
2010-02-25  7:11     ` Willy Tarreau
2010-03-01 19:57 ` John W. Linville [this message]
2010-03-01 23:37 ` Nick Kossifidis
2010-03-02 10:15 ` Holger Schurig

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=20100301195756.GF2961@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.