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]

Date:	Thu, 01 Apr 2010 00:26:22 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	w@....eu
Cc:	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

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