netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "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: Wed, 17 Jul 2013 18:55:04 -0700	[thread overview]
Message-ID: <1374112504.7622.49.camel@envy.home> (raw)
In-Reply-To: <20130716025954.GC26761@windriver.com>

On Mon, 2013-07-15 at 22:59 -0400, Paul Gortmaker wrote:

>    IMPORTANT:  Do not send new net-next content to netdev during the
>    period during which net-next tree is closed.
> 
>    Shortly after the two weeks have passed, (and vX.Y-rc1 is released) the
>    tree for net-next reopens to collect content for the next (vX.Y+1) release.

So I misunderstood this line apparently. I checked Linus tree:

$ git show v3.11-rc1
tag v3.11-rc1
Tagger: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Jul 14 15:18:41 2013 -0700

Linux 3.11-rc1

And seeing that rc1 had been tagged 3 days ago, submitted the pch_gbe
patch for MinnowBoard to netdev for net-next. David *very* politely :-)
asked me to resubmit when the net-next tree was open. It appears to me
then that we need to add a bit here about searching the archives
mentioned above for the last netdev-is-open message (I presume there is
a common subject format) to know whether a patch will be welcomed or
not.

I am not subscribed to netdev as I contribute only very rarely. Is it
considered a requirement that one be subscribed to netdev in order to
contribute? If so, we should add that here as well.


-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel

  parent reply	other threads:[~2013-07-18  1:55 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
2013-07-16 20:42 ` Joe Perches
2013-07-18  1:55 ` Darren Hart [this message]
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=1374112504.7622.49.camel@envy.home \
    --to=dvhart@linux.intel.com \
    --cc=davem@davemloft.net \
    --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).