This is a note to let you know that I've just added the patch titled
stable_kernel_rules: Add pointer to netdev-FAQ for network patches
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
stable_kernel_rules-add-pointer-to-netdev-faq-for-network-patches.patch
and it can be found in the queue-3.4 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From b76fc285337b6b256e9ba20a40cfd043f70c27af Mon Sep 17 00:00:00 2001
From: Dave Chiluk <chiluk@xxxxxxxxxxxxx>
Date: Tue, 24 Jun 2014 10:11:26 -0500
Subject: stable_kernel_rules: Add pointer to netdev-FAQ for network patches
From: Dave Chiluk <chiluk@xxxxxxxxxxxxx>
commit b76fc285337b6b256e9ba20a40cfd043f70c27af upstream.
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@xxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
Documentation/stable_kernel_rules.txt | 3 +++
1 file changed, 3 insertions(+)
--- a/Documentation/stable_kernel_rules.txt
+++ b/Documentation/stable_kernel_rules.txt
@@ -29,6 +29,9 @@ Rules on what kind of patches are accept
Procedure for submitting patches to the -stable tree:
+ - If the patch covers files in net/ or drivers/net please follow netdev stable
+ submission guidelines as described in
+ Documentation/networking/netdev-FAQ.txt
- Send the patch, after verifying that it follows the above rules, to
stable@xxxxxxxxxxxxxxx. You must note the upstream commit ID in the
changelog of your submission, as well as the kernel version you wish
Patches currently in stable-queue which might be from chiluk@xxxxxxxxxxxxx are
queue-3.4/stable_kernel_rules-add-pointer-to-netdev-faq-for-network-patches.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html