linux-kernel - Re: Elaboration on "Equivalent fix must already exist in Linus' tree"

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:	Mon, 2 Mar 2009 22:27:21 -0800
From:	Greg KH <greg@...ah.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	wireless <linux-wireless@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Elaboration on "Equivalent fix must already exist in Linus'
	tree"

On Mon, Mar 02, 2009 at 09:43:26PM -0800, Luis R. Rodriguez wrote:
> While extending the documentation for submitting Linux wireless bug
> reports [1] we note the stable series policy on patches -- that of
> having an equivalent fix already in Linus' tree. I find this
> documented in Documentation/stable_kernel_rules.txt but I'm curious if
> there is any other resource which documents this or elaborates on this
> a bit more.

Simple is better, do you really want a longer version of that same file?

Is there something confusing in it?

And as always, a simple:
	Cc: stable <stable@...nel.org>
in the patch itself is the easiest way to get it automatically included
in the next -stable releases after it hits Linus's tree.

What more do people want?  Personal invitations?

Is it time to break out the caligraphy pens and wax seals?

thanks,

greg k-h
--
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/