From: Randy Dunlap <rdunlap@infradead.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ondrej Mosnacek <omosnacek@gmail.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: linux-next: Tree for Dec 1 [crypto/aegis128.ko]
Date: Tue, 1 Dec 2020 13:42:12 -0800 [thread overview]
Message-ID: <271b8e92-b134-4447-e56e-c9fc9f60da94@infradead.org> (raw)
In-Reply-To: <0a1696a3-b4ca-be1f-f50d-2dcd903f074c@infradead.org>
On 12/1/20 1:37 PM, Randy Dunlap wrote:
> On 12/1/20 1:29 PM, Ard Biesheuvel wrote:
>> On Tue, 1 Dec 2020 at 20:53, Randy Dunlap <rdunlap@infradead.org> wrote:
>>>
>>> On 12/1/20 2:03 AM, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20201130:
>>>>
>>>
>>> on i386 or x86_64:
>>>
>>> CONFIG_CRYPTO_AEGIS128=m
>>> CONFIG_CRYPTO_AEGIS128_AESNI_SSE2=y
>>>
>>>
>>> ERROR: modpost: "crypto_aegis128_update_simd" [crypto/aegis128.ko] undefined!
>>>
>>
>> Fix posted here.
>> https://lore.kernel.org/linux-crypto/20201130122620.16640-1-ardb@kernel.org/
>>
>
thanks. That works for me also.
Acked-by: Randy Dunlap <rdunlap@infradead.org> # build-tested
>> Which compiler version are you using? This does not reproduce for me
>> with GCC 7.5.0
>>
>
> gcc (SUSE Linux) 7.5.0
>
> You could try the attached x86_64 randconfig file...
>
--
~Randy
prev parent reply other threads:[~2020-12-01 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 10:03 linux-next: Tree for Dec 1 Stephen Rothwell
2020-12-01 18:33 ` linux-next: Tree for Dec 1 (sound: SND_SOC_ADAU1372_SPI) Randy Dunlap
2020-12-01 19:52 ` linux-next: Tree for Dec 1 [crypto/aegis128.ko] Randy Dunlap
2020-12-01 21:29 ` Ard Biesheuvel
2020-12-01 21:37 ` Randy Dunlap
2020-12-01 21:42 ` Randy Dunlap [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=271b8e92-b134-4447-e56e-c9fc9f60da94@infradead.org \
--to=rdunlap@infradead.org \
--cc=ardb@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=omosnacek@gmail.com \
--cc=sfr@canb.auug.org.au \
/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).