linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kim, David" <david.kim@ncipher.com>
To: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	Greg KH <gregkh@linuxfoundation.org>,
	"Magee, Tim" <tim.magee@ncipher.com>
Subject: nCipher HSM kernel driver submission feedback request
Date: Fri, 13 Mar 2020 09:48:14 +0000	[thread overview]
Message-ID: <1584092894266.92323@ncipher.com> (raw)

Hi Herbert,

We've been working on getting this driver code upstreamed into drivers/misc since the end of last
year but things stalled a bit on our end. However, we are still interested in getting our submission
approved and would please like your assistance and feedback on this.

The driver code for the hardware is straightforward and does not contain any cryptographic
components as the cryptography is handled within the hardware's secure boundary. We have no
plans to use the linux kernel crypto APIs as our customers require compliance to the FIPS 140
standard or the eIDAS regulations.

Here is a link to the previous email I sent, which also contains more background links to our initial
discussions with Greg and the actual patch.

https://marc.info/?l=linux-crypto-vger&m=157918288423889&w=2

Can I please have your approval on this submission?

Thanks,
Dave


David Kim
Senior Software Engineer
Tel: +44 1223 703449

nCipher Security
One Station Square
Cambridge CB1 2GA
United Kingdom


             reply	other threads:[~2020-03-13  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  9:48 Kim, David [this message]
2020-03-13 10:09 ` nCipher HSM kernel driver submission feedback request Greg KH
2020-03-16 10:44   ` Kim, David
2020-03-16 11:23     ` Greg KH
2020-03-23  6:49 ` Jason A. Donenfeld
2020-03-23 13:32   ` Kim, David
2020-03-23 13:59     ` Greg KH
2020-04-17 15:12       ` Kim, David

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=1584092894266.92323@ncipher.com \
    --to=david.kim@ncipher.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=tim.magee@ncipher.com \
    /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;
as well as URLs for NNTP newsgroup(s).