linux-kernel - Re: [GIT PULL] Keyrings patches

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.02.1309120141280.4317@tundra.namei.org>
Date:	Thu, 12 Sep 2013 01:41:42 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	David Howells <dhowells@...hat.com>
cc:	simo@...hat.com, zohar@...ux.vnet.ibm.com, keyrings@...ux-nfs.org,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Keyrings patches

On Tue, 10 Sep 2013, David Howells wrote:

> James Morris <jmorris@...ei.org> wrote:
> 
> > > > This missed the merge for 3.12.  Do you want me to queue the changes up, 
> > > > or do you want to send a pull request again after -rc1 ?
> > > 
> > > Can you queue them up now in your 'next' branch?
> > 
> > Nope, new patches can't go into -next until -rc1.
> 
> I think I misunderstood your offer.  When you said "to queue the changes up"
> did you mean for immediate passage to Linus?  If so, is it too late for that?

Nope, I meant for -next :)


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