[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR04MB44458463C3FFBF7C2D99B4DE8C490@VI1PR04MB4445.eurprd04.prod.outlook.com>
Date: Fri, 22 Nov 2019 10:29:01 +0000
From: Iuliana Prodan <iuliana.prodan@....com>
To: Herbert Xu <herbert@...dor.apana.org.au>
CC: Horia Geanta <horia.geanta@....com>,
Aymen Sghaier <aymen.sghaier@....com>,
"David S. Miller" <davem@...emloft.net>,
Tom Lendacky <thomas.lendacky@....com>,
Gary Hook <gary.hook@....com>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [PATCH 01/12] crypto: add helper function for akcipher_request
On 11/22/2019 11:08 AM, Herbert Xu wrote:
> On Mon, Nov 18, 2019 at 12:30:34AM +0200, Iuliana Prodan wrote:
>>
>> diff --git a/include/crypto/akcipher.h b/include/crypto/akcipher.h
>> index 6924b09..4365edd 100644
>> --- a/include/crypto/akcipher.h
>> +++ b/include/crypto/akcipher.h
>> @@ -170,6 +170,12 @@ static inline struct crypto_akcipher *crypto_akcipher_reqtfm(
>> return __crypto_akcipher_tfm(req->base.tfm);
>> }
>>
>> +static inline struct akcipher_request *akcipher_request_cast(
>> + struct crypto_async_request *req)
>> +{
>> + return container_of(req, struct akcipher_request, base);
>> +}
>
> This should go into include/crypto/internal/akcipher.h as it's
> only used by implementors.
>
> But having reviewed the subsequent patches I think we shouldn't
> have this function at all.
>
Why can't we use this? There are similar functions for
skcipher/aead/ahash and they are all in include/crypto.
Thanks,
Iulia
Powered by blists - more mailing lists