From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Stephen Hemminger <shemminger@vyatta.com>,
Greg KH <greg@kroah.com>, "H. Peter Anvin" <hpa@kernel.org>
Cc: Benoit PAPILLAULT <benoit.papillault@free.fr>,
linux-wireless <linux-wireless@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: 802.11 development process - extended documentation
Date: Wed, 24 Feb 2010 21:11:23 -0800 [thread overview]
Message-ID: <43e72e891002242111x74f15f67y491ea7351d9c7b67@mail.gmail.com> (raw)
In-Reply-To: <20100224183744.52732c77@nehalam>
On Wed, Feb 24, 2010 at 6:37 PM, Stephen Hemminger
<shemminger@vyatta.com> wrote:
> On Thu, 25 Feb 2010 03:34:30 +0100
> Benoit PAPILLAULT <benoit.papillault@free.fr> wrote:
>
>> Luis R. Rodriguez a écrit :
>> > On Wed, Feb 24, 2010 at 4:43 PM, Luis R. Rodriguez <mcgrof@gmail.com> wrote:
>> >
>> >> On Wed, Feb 24, 2010 at 4:34 PM, Benoit PAPILLAULT
>> >> <benoit.papillault@free.fr> wrote:
>> >>
>> >>> 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
>
> The part that is missing is the -stable kernel tree (Greg KH).
Indeed, so I was unsure how the the linux-2.6-allstable gets
maintained yet, what that pulls from, and how linux-2.6-stable.git
gets put together. If someone has time to explain how that to works to
me I'd gladly add that.
> As a distro maintainer, I find the stable kernel tree the most important of all!
Sure.
> More important than the compat-wireless tree (sorry Luis).
Heh, no offense taken, remember this is for 802.11, that's why I added
that stuff. I often have to explain how that stuff works too.
Luis
next prev parent reply other threads:[~2010-02-25 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 0:18 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 [this message]
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
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=43e72e891002242111x74f15f67y491ea7351d9c7b67@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=benoit.papillault@free.fr \
--cc=greg@kroah.com \
--cc=hpa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=shemminger@vyatta.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
all inboxes | Powered by JetHome®