From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au, corbet@lwn.net,
keescook@chromium.org, qat-linux@intel.com, jwboyer@redhat.com,
richard@nod.at, linux-kernel@vger.kernel.org, steved@redhat.com,
dhowells@redhat.com, vgoyal@redhat.com,
james.l.morris@oracle.com, jkosina@suse.cz,
zohar@linux.vnet.ibm.com, davem@davemloft.net,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] crypto: add PKE API
Date: Fri, 01 May 2015 10:30:37 -0700 [thread overview]
Message-ID: <5543B83D.1090606@intel.com> (raw)
In-Reply-To: <1788430.tPLLCmOF11@tauon>
Hi Stephan,
On 05/01/2015 12:24 AM, Stephan Mueller wrote:
>> +struct public_key;
>> >+struct public_key_signature;
> Wouldn't it make sense to move the struct definitions here and have them
> documented?
I'm not sure if they belong here. I think we can add some documentation
without moving them.
>> +struct pke_alg {
>> >+ int (*sign)(struct pke_request *pkereq);
>> >+ int (*verify)(struct pke_request *pkereq);
>> >+ int (*encrypt)(struct pke_request *pkereq);
>> >+ int (*decrypt)(struct pke_request *pkereq);
>> >+
>> >+ u8 pub_mpis; /* Number of MPIs in public key */
>> >+ u8 sec_mpis; /* Number of MPIs in secret key */
>> >+ u8 sig_mpis; /* Number of MPIs in a signature */
> May I ask that for such new structs we add some documentation? Currently, I am
> unclear on what MPIs are. E.g. if somebody needs to add, say, Curve 25519,
> what shall he add here?
Sure, I'll add some description.
>
> Up to here I am volunteering to add the documentation comments.
>
> But for the following functions, I am not sure how they are supposed to be
> used correctly. Thus, can you add the documentation for them or at least give
> me a hint so that I can add the documentation?
Same here, I'll add something. Thanks for volunteering.
You did a good job documenting the rest and your help will be appreciated.
next prev parent reply other threads:[~2015-05-01 17:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 22:36 [PATCH RFC 0/2] crypto: Introduce Public Key Encryption API Tadeusz Struk
2015-04-30 22:36 ` [PATCH RFC 1/2] crypto: add PKE API Tadeusz Struk
2015-04-30 22:43 ` Herbert Xu
2015-04-30 23:04 ` Tadeusz Struk
2015-05-01 7:24 ` Stephan Mueller
2015-05-01 17:30 ` Tadeusz Struk [this message]
2015-05-01 16:04 ` David Howells
2015-05-01 18:17 ` Tadeusz Struk
2015-05-03 0:07 ` Herbert Xu
2015-05-04 19:26 ` Tadeusz Struk
2015-05-05 1:33 ` Herbert Xu
2015-04-30 22:36 ` [PATCH RFC 2/2] crypto: RSA: KEYS: convert rsa and public key to new " Tadeusz Struk
2015-05-01 16:21 ` David Howells
2015-05-01 19:27 ` Tadeusz Struk
2015-05-01 8:47 ` [PATCH RFC 0/2] crypto: Introduce Public Key Encryption API Jean Delvare
2015-05-01 17:32 ` Tadeusz Struk
2015-05-01 15:53 ` David Howells
2015-05-04 13:16 ` Horia Geantă
2015-05-04 20:42 ` Tadeusz Struk
2015-05-06 11:31 ` Horia Geantă
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=5543B83D.1090606@intel.com \
--to=tadeusz.struk@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=james.l.morris@oracle.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=richard@nod.at \
--cc=smueller@chronox.de \
--cc=steved@redhat.com \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.