From: Benjamin Poirier <benjamin.poirier@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
"David S. Miller" <davem@davemloft.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org
Subject: Re: [RFC] Any value in having a netdev FAQ?
Date: Thu, 18 Jul 2013 14:21:00 -0400 [thread overview]
Message-ID: <20130718182100.GA10853@d2.synalogic.ca> (raw)
In-Reply-To: <51E6B5BE.6050505@windriver.com>
On 2013/07/17 11:18, Paul Gortmaker wrote:
> On 13-07-16 04:32 PM, Darren Hart wrote:
> >>
> >> Aside from subsystems like that mentioned above, all network related linux
> >> development (i.e. RFC, review, comments, etc) takes place on netdev.
> >>
> >
> >
> > Should LKML be Cc'd? I assume so...
>
> No, not unless there is a good reason to do so.
>
That advice would run counter to what's in
Documentation/SubmittingPatches:
6) Select your CC (e-mail carbon copy) list.
Unless you have a reason NOT to do so, CC linux-kernel@vger.kernel.org.
Also, get-maintainers includes lkml all the time.
next prev parent reply other threads:[~2013-07-18 18:21 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
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 [this message]
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=20130718182100.GA10853@d2.synalogic.ca \
--to=benjamin.poirier@gmail.com \
--cc=davem@davemloft.net \
--cc=dvhart@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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).