linux-kernel - Re: [PATCH] SubmittingPatches: Clarify requirements for patches directed toward stable

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]

Date:	Thu, 14 May 2015 13:53:33 -0400
From:	Jonathan Corbet <corbet@....net>
To:	Luke Dashjr <luke@...hjr.org>
Cc:	trivial@...nel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] SubmittingPatches: Clarify requirements for patches
 directed toward stable

On Thu, 14 May 2015 00:06:48 +0000
Luke Dashjr <luke@...hjr.org> wrote:

> I misunderstood this section as simply asking me to add an email Cc, and
> was unaware of the existence of Documentation/stable_kernel_rules.txt.
> Hopefully this clarification will help save maintainers and new/rare
> submitters time in the future.

It's a good change, but I think it's worth going a bit further: you
really don't need to email the patch to stable@ at all if the CC line
appears in the patch itself.  The patch will automatically come to the
attention of the right folks once the patch hits the mainline.

jon
--
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/