From: Till Kamppeter <till.kamppeter@gmail.com>
To: Jeff Licquia <jeff@licquia.org>, Eric Searcy <eric@linuxfoundation.org>
Cc: "Luis R. Rodriguez" <mcgrof@frijolero.org>,
David Miller <davem@davemloft.net>,
Stephen Hemminger <shemminger@vyatta.com>,
nic-devel <nic-devel@qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Wiki page for Ethernet drivers
Date: Wed, 15 Feb 2012 18:08:17 +0100 [thread overview]
Message-ID: <4F3BE681.4040607@gmail.com> (raw)
In-Reply-To: <CAB=NE6WdaPPVmq7+oSsjbN+4mcH4zTqXHqu5iAAOFzJfhL8AkQ@mail.gmail.com>
Jeff, Eric, can someone of you help here? Thanks.
Till
On 02/15/2012 05:58 PM, Luis R. Rodriguez wrote:
> Folks,
>
> can I get edit rights to edit this page:
>
> https://www.linuxfoundation.org/collaborate/workgroups/networking/mainpage
>
> or any subsection under networking? I'd like to make a home page for
> Ethernet drivers. So far I've stuffed this under the wireless wiki but
> this is not the appropriate place for it:
>
> http://wireless.kernel.org/en/users/Drivers/ethernet
>
> A few of our guys would also use this to keep editing specifically the
> new alx driver documentation. If this is not the right place can you
> please point me to where we can add Ethernet driver documentation
> updates? As I have noted before, the Documentation/ directory of the
> kernel does not seem appropriate for this. We have had quite a bit of
> success in documenting Wireless drivers through the wireless wiki and
> I'd like to continue that tradition.
>
> Luis
>
next prev parent reply other threads:[~2012-02-15 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 16:58 Wiki page for Ethernet drivers Luis R. Rodriguez
2012-02-15 17:08 ` Till Kamppeter [this message]
2012-02-17 1:26 ` 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=4F3BE681.4040607@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=davem@davemloft.net \
--cc=eric@linuxfoundation.org \
--cc=jeff@licquia.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=netdev@vger.kernel.org \
--cc=nic-devel@qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).