From: Benoit PAPILLAULT <benoit.papillault@free.fr>
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: Thu, 25 Feb 2010 01:34:36 +0100 [thread overview]
Message-ID: <4B85C59C.3010602@free.fr> (raw)
In-Reply-To: <43e72e891002241618w10d5c45ar9303f074d0228217@mail.gmail.com>
Luis R. Rodriguez a écrit :
> 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.
>
> Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
Nice (especially the picture)! However, Johannes has its picture in the
text, but not in the diagram and the opposite for ... you I guess
(picture on the left hand). Just a quick review. I still need to fully
understand the "patch" stream...
Regards,
Benoit
next prev parent reply other threads:[~2010-02-25 0:34 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 [this message]
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
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=4B85C59C.3010602@free.fr \
--to=benoit.papillault@free.fr \
--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.