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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Sep 2014 14:23:48 +0100 From: David Howells <dhowells@...hat.com> To: James Morris <jmorris@...ei.org> Cc: dhowells@...hat.com, keyrings@...ux-nfs.org, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [GIT PULL] KEYS: Fixes for keyrings James Morris <jmorris@...ei.org> wrote: > > > No, if they go direct to Linus, they don't go into -next. > > > > Can you then sync your -next branch to Linus after Linus takes them please? > > Nope, I only want to sync on point releases unless absolutely necessary. In that case, can you please just pull the request in this message that I sent you: [GIT PULL] KEYS: Changes for keyrings for security/next It has the aforementioned fixes and the stuff for -next both. If you can just pull the lot into your -next branch rather than sending the fixes upstream at this point. David -- 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