| 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
| ||
|
Date: Wed, 25 Jul 2012 23:48:52 +0100 From: Mel Gorman <mgorman@...e.de> To: Greg KH <greg@...ah.com> Cc: Stable <stable@...r.kernel.org>, Linux-MM <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 00/34] Memory management performance backports for -stable V2 On Wed, Jul 25, 2012 at 03:30:57PM -0700, Greg KH wrote: > > <SNIP> > > All of the patches will apply to 3.0-stable but the ordering of the > > patches is such that applying them to 3.2-stable and 3.4-stable should > > be straight-forward. > > I can't find any of these that should have gone to 3.4-stable, given > that they all were included in 3.4 already, right? > Yes, you're right. At the time I wrote the changelog I had patches belonging to 3.5 included. I later decided to drop them until after 3.5 was out. It was potentially weird to have a 3.0-stable kernel with patches that were not in a released 3.x.0 kernel. Besides, they were very low priority. I forgot to update the changelog to match. > I've queued up the whole lot for the 3.0-stable tree, thanks so much for > providing them. > Thanks for reviewing them in detail and getting the flaws corrected. I expect it'll be a bit more smooth if/when I do something like this again. -- Mel Gorman SUSE Labs -- 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/
Powered by blists - more mailing lists