| 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: Mon, 10 Aug 2009 11:55:35 +0200 From: Andi Kleen <andi@...stfloor.org> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Andi Kleen <andi@...stfloor.org>, akpm@...ux-foundation.org, linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org> Subject: Re: hwpoison merge for linux-next / 2.6.32 > OK, I have added this today. Thanks. > What I tell everyone: all patches/commits in the tree/series must > have been: > > posted to a relevant mailing list > reviewed > unit tested > destined for the next merge window (or the current release) all true for hwpoison. > > *before* they are included. The linux-next tree is for integration > testing and to lower the impact of conflicts between subsystems in the > next merge window. > > Basically, this should be just what you would send to Linus or in this > case, Ingo, (or ask him to fetch). It is allowed to be rebased if you This is practially all generic MM or VFS code, nothing for Ingo. The only part that should concern anything Ingo maintains is a one tiny patch for x86 in the patch series. While that could be in theory separated out I don't think it makes too much sense (the patch wouldn't build without the rest of hwpoison) -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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