All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH v3 2/2] crypto: akcipher - Changes to asymmetric key API
Date: Thu, 1 Oct 2015 08:17:49 -0700	[thread overview]
Message-ID: <560D4E9D.1060502@intel.com> (raw)
In-Reply-To: <20151001151519.GA28373@gondor.apana.org.au>

On 10/01/2015 08:15 AM, Herbert Xu wrote:
> On Thu, Oct 01, 2015 at 07:52:32AM -0700, Tadeusz Struk wrote:
>> On 10/01/2015 06:45 AM, Herbert Xu wrote:
>>> On Tue, Sep 22, 2015 at 09:34:03AM -0700, Tadeusz Struk wrote:
>>>>
>>>>  struct akcipher_request {
>>>>  	struct crypto_async_request base;
>>>> -	void *src;
>>>> -	void *dst;
>>>> -	unsigned int src_len;
>>>> -	unsigned int dst_len;
>>>> +	struct scatterlist *src;
>>>> +	struct scatterlist *dst;
>>>> +	unsigned int out_len;
>>>
>>> I think src_len/dst_len should be kept as the SG list may contain
>>> more entries than the ones that you need to process.
>>>
>> Herbert,
>> Could you still apply it and the "Add mpi sgl helpers" on top
>> and I'll add the src_len/dst_len in an incremental patch?
>> It will make it easier for me.
> 
> Well I don't think we need out_len with dst_len being there so
> this would be adding and then removing out_len for no good reason.
> 

Technically it would be renaming instead of adding and then removing :)

      reply	other threads:[~2015-10-01 15:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 16:33 [PATCH v3 0/2] crypto: akcipher - Changes to asymmetric key API Tadeusz Struk
2015-09-22 16:33 ` [PATCH v3 1/2] lib/scatterlist: Add sg_len helper Tadeusz Struk
2015-09-22 16:34 ` [PATCH v3 2/2] crypto: akcipher - Changes to asymmetric key API Tadeusz Struk
2015-10-01 13:45   ` Herbert Xu
2015-10-01 14:52     ` Tadeusz Struk
2015-10-01 15:15       ` Herbert Xu
2015-10-01 15:17         ` Tadeusz Struk [this message]

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=560D4E9D.1060502@intel.com \
    --to=tadeusz.struk@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=qat-linux@intel.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.