From: Dave Chiluk <chiluk@canonical.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
stable@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, davem@davemloft.net
Cc: Dave Chiluk <chiluk@canonical.com>
Subject: [PATCH] stable_kernel_rules: Add pointer to netdev-FAQ for network patches
Date: Mon, 23 Jun 2014 11:22:28 -0500 [thread overview]
Message-ID: <1403540548-17152-1-git-send-email-chiluk@canonical.com> (raw)
Stable_kernel_rules should point submitters of network stable patches to the
netdev_FAQ.txt as requests for stable network patches should go to netdev
first.
Signed-off-by: Dave Chiluk <chiluk@canonical.com>
---
Documentation/stable_kernel_rules.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/stable_kernel_rules.txt b/Documentation/stable_kernel_rules.txt
index cbc2f03..216c893 100644
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -29,6 +29,9 @@ Rules on what kind of patches are accepted, and which ones are not, into the
Procedure for submitting patches to the -stable tree:
+ - If the patch covers the networking subsystem please follow netdev stable
+ sumissision guidelines as described in
+ Documentation/networking/netdev-FAQ.txt
- Send the patch, after verifying that it follows the above rules, to
stable@vger.kernel.org. You must note the upstream commit ID in the
changelog of your submission, as well as the kernel version you wish
--
1.9.1
next reply other threads:[~2014-06-23 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 16:22 Dave Chiluk [this message]
2014-06-23 16:38 ` [PATCH] stable_kernel_rules: Add pointer to netdev-FAQ for network patches Joe Perches
2014-06-23 17:24 ` [PATCH v2] " Dave Chiluk
2014-06-24 12:43 ` Bjørn Mork
2014-06-24 15:11 ` [PATCH v3] " Dave Chiluk
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=1403540548-17152-1-git-send-email-chiluk@canonical.com \
--to=chiluk@canonical.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stable@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