From: "Dey, Megha" <megha.dey@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
"Megha Dey" <megha.dey@linux.intel.com>
Subject: RE: [PATCH V2 2/2] crypto : async implementation for sha1-mb
Date: Tue, 7 Jun 2016 18:10:14 +0000 [thread overview]
Message-ID: <C440BA31B54DCD4AAC682D2365C8FEE703C662A9@ORSMSX111.amr.corp.intel.com> (raw)
In-Reply-To: <20160607103515.GB325@gondor.apana.org.au>
-----Original Message-----
From: Herbert Xu [mailto:herbert@gondor.apana.org.au]
Sent: Tuesday, June 7, 2016 3:35 AM
To: Dey, Megha <megha.dey@intel.com>
Cc: tim.c.chen@linux.intel.com; davem@davemloft.net; linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org; Yu, Fenghua <fenghua.yu@intel.com>; Megha Dey <megha.dey@linux.intel.com>
Subject: Re: [PATCH V2 2/2] crypto : async implementation for sha1-mb
On Thu, Jun 02, 2016 at 07:53:50PM -0700, Megha Dey wrote:
>
> + struct ahash_alg *shash = crypto_ahash_alg(tfm);
>
> /* alignment is to be done by multi-buffer crypto algorithm if
> needed */
>
> - return shash->finup(desc, NULL, 0, req->result);
> + return shash->finup(desc);
You're still poking in the guts of the API. Now that it's a real ahash you don't need to do that.
Just do crypto_ahash_finup. That way you don't need to export crypto_ahsh_alg either.
> I have made these changes and re-sent the patch.
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2016-06-07 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 2:53 [PATCH V2 0/2] Implementation of an async interface for sha1-mb Megha Dey
2016-06-03 2:53 ` [PATCH V2 1/2] crypto: sha1-mb - stylistic cleanup Megha Dey
2016-06-07 10:44 ` Herbert Xu
2016-06-03 2:53 ` [PATCH V2 2/2] crypto : async implementation for sha1-mb Megha Dey
2016-06-07 10:35 ` Herbert Xu
2016-06-07 18:10 ` Dey, Megha [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=C440BA31B54DCD4AAC682D2365C8FEE703C662A9@ORSMSX111.amr.corp.intel.com \
--to=megha.dey@intel.com \
--cc=davem@davemloft.net \
--cc=fenghua.yu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megha.dey@linux.intel.com \
--cc=tim.c.chen@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 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).