linux-kernel - Re: [Keyrings] [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] [day] [month] [year] [list]

Message-ID: <1411047801.2076.21.camel@dhcp-9-2-203-236.watson.ibm.com>
Date:	Thu, 18 Sep 2014 09:43:21 -0400
From:	Mimi Zohar <zohar@...ux.vnet.ibm.com>
To:	David Howells <dhowells@...hat.com>
Cc:	James Morris <jmorris@...ei.org>, keyrings@...ux-nfs.org,
	linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [Keyrings] [GIT PULL] KEYS: Fixes for keyrings

On Thu, 2014-09-18 at 14:23 +0100, 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.
> 
> 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, consider copying stable to automatically have bug fixes
backported.  After your "signed-off-by" add "Cc:
<stable@...r.kernel.org>  <release>" to indicate which kernel release.

Mimi

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