linux-kernel - Re: [GIT PULL] KEYS: Fixes for keyrings

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: <alpine.LRH.2.11.1409181712020.1998@namei.org>
Date:	Thu, 18 Sep 2014 17:12:36 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	David Howells <dhowells@...hat.com>
cc:	keyrings@...ux-nfs.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] KEYS: Fixes for keyrings

On Thu, 18 Sep 2014, David Howells wrote:

> 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.


-- 
James Morris
<jmorris@...ei.org>

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