From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Cc: Willy Tarreau <w@1wt.eu>,
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:19:41 -0800 [thread overview]
Message-ID: <43e72e891002242119u77fdfd30m2d17a1e48fe2e712@mail.gmail.com> (raw)
In-Reply-To: <3f9a31f41002242053r169255d2hf2585aeb55174a92@mail.gmail.com>
On Wed, Feb 24, 2010 at 8:53 PM, Jaswinder Singh Rajput
<jaswinderlinux@gmail.com> wrote:
> Hello Luis,
>
> On Thu, Feb 25, 2010 at 5:48 AM, Luis R. Rodriguez <mcgrof@gmail.com> 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.
>>
>
> Thanks for the beautiful documentation.
Thanks :)
> Is this also applicable for Linux 2.4
Not at all.
> What is the status of Wireless in Linux 2.4
Heh, umm, I have no clue. Dead?
Luis
next prev parent reply other threads:[~2010-02-25 5:20 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
2010-02-25 4:53 ` Jaswinder Singh Rajput
2010-02-25 5:19 ` Luis R. Rodriguez [this message]
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=43e72e891002242119u77fdfd30m2d17a1e48fe2e712@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=w@1wt.eu \
/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
Powered by JetHome