From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] KEYS: Miscellaneous small changes
Date: Fri, 20 May 2016 08:49:48 +0100 [thread overview]
Message-ID: <26720.1463730588@warthog.procyon.org.uk> (raw)
Hi James,
Can you pull these miscellaneous small changes into your next tree and pass
them along to Linus? There's nothing that should be ground breaking here:
(1) MAINTAINERS record update.
(2) Add a MODULE_LICENSE tag to the ASN.1 decoder.
(3) Fix the PKCS#7 test key type to search the correct keyring.
Thanks,
David
---
The following changes since commit a6926cc989eb8e3349ae9b858177608e86f7257c:
Merge branch 'stable-4.7' of git://git.infradead.org/users/pcmoore/selinux into next (2016-05-06 09:31:34 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-next-20160511
for you to fetch changes up to 75aeddd12f205d07b36ed76db3426e974b8f2a21:
MAINTAINERS: Update keyrings record and add asymmetric keys record (2016-05-11 14:36:14 +0100)
----------------------------------------------------------------
Keyrings changes for next
----------------------------------------------------------------
David Howells (2):
KEYS: The PKCS#7 test key type should use the secondary keyring
MAINTAINERS: Update keyrings record and add asymmetric keys record
Tudor Ambarus (1):
lib: asn1_decoder - add MODULE_LICENSE("GPL")
MAINTAINERS | 12 ++++++++++++
crypto/asymmetric_keys/pkcs7_key_type.c | 2 +-
lib/asn1_decoder.c | 3 +++
3 files changed, 16 insertions(+), 1 deletion(-)
reply other threads:[~2016-05-20 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=26720.1463730588@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.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®