linux-kernel - Re: [PATCH v2] stable_kernel_rules: Add pointer to netdev-FAQ for network patches

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <878uomwk8g.fsf@nemi.mork.no>
Date:	Tue, 24 Jun 2014 14:43:59 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	Dave Chiluk <chiluk@...onical.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Randy Dunlap <rdunlap@...radead.org>, stable@...r.kernel.org,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	joe@...ches.com, davem@...emloft.net
Subject: Re: [PATCH v2] stable_kernel_rules: Add pointer to netdev-FAQ for network patches

Dave Chiluk <chiluk@...onical.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@...onical.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/