From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
ebiggers@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] keys: Miscellaneous fixes
Date: Fri, 15 Feb 2019 06:01:47 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1902150601280.17510@namei.org> (raw)
In-Reply-To: <155016118572.8115.3243711127043478822.stgit@warthog.procyon.org.uk>
On Thu, 14 Feb 2019, David Howells wrote:
>
> Hi James,
>
> Here are some keyrings fixes.
For which kernel, -rc or 5.1?
--
James Morris
<jmorris@namei.org>
next prev parent reply other threads:[~2019-02-14 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 16:19 David Howells
2019-02-14 16:20 ` [PATCH 1/4] KEYS: allow reaching the keys quotas exactly David Howells
2019-02-14 16:20 ` [PATCH 2/4] assoc_array: Fix shortcut creation David Howells
2019-02-14 16:20 ` [PATCH 3/4] keys: Fix dependency loop between construction record and auth key David Howells
2019-02-14 16:20 ` [PATCH 4/4] keys: Timestamp new keys David Howells
2019-02-14 19:01 ` James Morris [this message]
2019-02-15 16:54 ` [PATCH 0/4] keys: Miscellaneous fixes David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.21.1902150601280.17510@namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®