From: <Tudor.Ambarus@microchip.com>
To: <herbert@gondor.apana.org.au>, <yuehaibing@huawei.com>
Cc: <davem@davemloft.net>, <cyrille.pitchen@atmel.com>,
<linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] crypto: atmel - Fix randbuild error
Date: Tue, 12 Nov 2019 12:16:06 +0000 [thread overview]
Message-ID: <bfe0db64-209e-603d-759b-70ac2f691007@microchip.com> (raw)
In-Reply-To: <7988a8aa-e0e7-b031-7e79-fb9c5bd4e81a@microchip.com>
On 11/12/2019 01:56 PM, Tudor.Ambarus@microchip.com wrote:
>
>
> On 11/12/2019 04:15 AM, Herbert Xu wrote:
>> External E-Mail
>>
>>
>> On Tue, Nov 12, 2019 at 10:13:50AM +0800, Herbert Xu wrote:
>>>
>>> What we should do instead is turn DEV_ATMEL_AUTHENC into a bool,
>>
>> Oh and DEV_ATMEL_AUTHENC should also depend on CRYPTO_DEV_ATMEL_AES
>> and lose all its selects.
>>
>
> How about getting rid of CONFIG_CRYPTO_DEV_ATMEL_AUTHENC entirely?
>
mm, we can't do this because atmel-aes and atmel-sha are treated as two
separated entities.
next prev parent reply other threads:[~2019-11-12 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 13:39 [PATCH -next] crypto: atmel - Fix randbuild error YueHaibing
2019-11-12 2:13 ` Herbert Xu
2019-11-12 2:15 ` Herbert Xu
2019-11-12 11:56 ` Tudor.Ambarus
2019-11-12 12:16 ` Tudor.Ambarus [this message]
2019-11-12 7:24 ` [PATCH v2 -next] crypto: atmel - Fix build error of CRYPTO_AUTHENC YueHaibing
2019-11-12 12:19 ` Tudor.Ambarus
2019-11-13 9:55 ` [PATCH v3 " YueHaibing
2019-11-22 11:02 ` Herbert Xu
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=bfe0db64-209e-603d-759b-70ac2f691007@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=cyrille.pitchen@atmel.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@huawei.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).