From: David Howells <dhowells@redhat.com>
To: jmorris@namei.org, herbert@gondor.apana.org.au
Cc: dhowells@redhat.com, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Moving asymmetric keys from crypto/ to security/keys/
Date: Wed, 13 Apr 2016 13:45:38 +0100 [thread overview]
Message-ID: <776.1460551538@warthog.procyon.org.uk> (raw)
Hi James, Herbert,
Since the actual crypto bits (RSA) have been extracted from the asymmetric
keys code and moved to base crypto, shall I move the asymmetric_keys/ subdir
over to security/keys/?
If so, how best to do it? I'm thinking that it might be best for me to create
a git branch that effects the change and then have both of you merge it so
that when Linus pulls your stuff in the next merge window git just handles it.
That said, there is a change to the PKCS#7 code in Herbert's tree that's not
in security/next or upstream which complicates matters - though possibly this
being fixed up in the merge will be handled by git.
David
reply other threads:[~2016-04-13 12:45 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=776.1460551538@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@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®