From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: David Miller <davem@davemloft.net>
Cc: <dvhart@linux.intel.com>, <gregkh@linuxfoundation.org>,
<netdev@vger.kernel.org>
Subject: Re: [RFC] Any value in having a netdev FAQ?
Date: Wed, 17 Jul 2013 11:08:29 -0400 [thread overview]
Message-ID: <51E6B36D.8010904@windriver.com> (raw)
In-Reply-To: <20130716.130514.559781233978406598.davem@davemloft.net>
On 13-07-16 04:05 PM, David Miller wrote:
> From: Paul Gortmaker <paul.gortmaker@windriver.com>
> Date: Mon, 15 Jul 2013 22:59:54 -0400
>
>> I was wondering if you think there is value in having a netdev-faq type
>> document available -- perhaps as a vger mailout to new subscribers or
>> similar? For example, I have lost count of the number of times that you
>> have had to tell people that net-next is closed during the merge window.
>> But you would probably be right in telling me that those same people don't
>> read documentation. Well, that aside, I suppose answering my question
>> is easier when there is a proposed starting point for content.
>>
>> To that end, I've tried to collect a starting point based on repeated
>> questions/corrections that I've seen over the years. I've added Greg to
>> the Cc: in order to ensure I've captured the netdev-stable interaction
>> correctly, and I've thrown Darren under the bus as a random content
>> reviewer, since he has expressed an interest in documentation recently.
>>
>> Below is a possible starting point for content. Many answers I have
>> written are from memory, long after losing links to netdev threads that
>> served as evidence for the answers, so apologies in advance if I have
>> failed to recall correctly the specific details in which you would like
>> to see things done.
>
> Thanks a lot for writing this, it is useful.
>
> I think it's easier if this lives somewhere under
> Documentation/networking in the kernel tree, then we can just point
> people at it.
>
> What do you think?
Sounds fine to me, I'll make some of the corrections Darren pointed out
and send it along as a patch.
next prev parent reply other threads:[~2013-07-17 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 2:59 [RFC] Any value in having a netdev FAQ? Paul Gortmaker
2013-07-16 20:05 ` David Miller
2013-07-16 20:34 ` Darren Hart
2013-07-16 20:35 ` Darren Hart
2013-07-17 15:08 ` Paul Gortmaker [this message]
2013-07-16 20:32 ` Darren Hart
2013-07-17 15:18 ` Paul Gortmaker
2013-07-17 15:56 ` Joe Perches
2013-07-18 18:21 ` Benjamin Poirier
2013-07-16 20:42 ` Joe Perches
2013-07-18 1:55 ` Darren Hart
2013-07-18 13:33 ` Paul Gortmaker
2013-07-18 17:53 ` Rick Jones
2013-07-18 2:32 ` Hannes Frederic Sowa
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=51E6B36D.8010904@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=davem@davemloft.net \
--cc=dvhart@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
/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).