linux-kernel - Re: [Stable-review] 4 stable kernel review cycles starting

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: <4BB4823F.7040408@s5r6.in-berlin.de>
Date:	Thu, 01 Apr 2010 13:23:43 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	David Miller <davem@...emloft.net>
CC:	w@....eu, gregkh@...e.de, david@...morbit.com,
	linux-kernel@...r.kernel.org, stable@...nel.org,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	stable-review@...nel.org, alan@...rguk.ukuu.org.uk
Subject: Re: [Stable-review] 4 stable kernel review cycles starting

David Miller wrote:
> From: Willy Tarreau <w@....eu>
> Date: Thu, 1 Apr 2010 06:40:48 +0200
> 
>> For this reason, IMHO it helps when submitters can indicate in each
>> patch the mainline equivalent ID, or alternatively that it's pointless
>> to look for it because the fix is much different.
> 
> I put this at the top of every networking/ide/sparc commit message
> for -stable submissions I make.
> 
> In fact I thought that was a requirement for -stable submissions?

It is a documented requirement, perhaps not very clearly worded in The
Submitter's Guide To Stable...
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=46cdf871d9970b9252469531f9efd4a17243bb0b
-- 
Stefan Richter
-=====-==-=- -=-- ----=
http://arcgraph.de/sr/
--
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/