From: "Bjørn Mork" <bjorn@mork.no>
To: Dave Chiluk <chiluk@canonical.com>
Cc: 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, joe@perches.com,
davem@davemloft.net
Subject: Re: [PATCH v2] stable_kernel_rules: Add pointer to netdev-FAQ for network patches
Date: Tue, 24 Jun 2014 14:43:59 +0200 [thread overview]
Message-ID: <878uomwk8g.fsf@nemi.mork.no> (raw)
In-Reply-To: <1403544280-21182-1-git-send-email-chiluk@canonical.com> (Dave Chiluk's message of "Mon, 23 Jun 2014 12:24:40 -0500")
Dave Chiluk <chiluk@canonical.com> writes:
> 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..a39a0d7 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 files in net/ or drivers/net please follow netdev stable
> + sumissision guidelines as described in
^^^^^^^^^^^
3 is a nice number :-)
Bjørn
next prev parent reply other threads:[~2014-06-24 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 16:22 [PATCH] stable_kernel_rules: Add pointer to netdev-FAQ for network patches Dave Chiluk
2014-06-23 16:38 ` Joe Perches
2014-06-23 17:24 ` [PATCH v2] " Dave Chiluk
2014-06-24 12:43 ` Bjørn Mork [this message]
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=878uomwk8g.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=chiluk@canonical.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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