From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: Neal Liu <neal_liu@aspeedtech.com>,
Johnny Huang <johnny_huang@aspeedtech.com>,
Dhananjay Phadke <dphadke@linux.microsoft.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
linux-aspeed@lists.ozlabs.org, linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: build failure of next-20220829 due to 108713a713c7 ("crypto: aspeed - Add HACE hash driver")
Date: Mon, 29 Aug 2022 11:00:38 +0100 [thread overview]
Message-ID: <YwyORp72cuDrVYdA@debian> (raw)
Hi All,
The builds of arm allmodconfig have failed to build next-20220829 with
the error:
ERROR: modpost: "aspeed_register_hace_hash_algs" [drivers/crypto/aspeed/aspeed_crypto.ko] undefined!
ERROR: modpost: "aspeed_unregister_hace_crypto_algs" [drivers/crypto/aspeed/aspeed_crypto.ko] undefined!
ERROR: modpost: "aspeed_register_hace_crypto_algs" [drivers/crypto/aspeed/aspeed_crypto.ko] undefined!
ERROR: modpost: "aspeed_unregister_hace_hash_algs" [drivers/crypto/aspeed/aspeed_crypto.ko] undefined!
git bisect pointed to 108713a713c7 ("crypto: aspeed - Add HACE hash driver")
I will be happy to test any patch or provide any extra log if needed.
--
Regards
Sudip
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-08-29 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 10:00 Sudip Mukherjee (Codethink) [this message]
2022-08-29 10:04 ` build failure of next-20220829 due to 108713a713c7 ("crypto: aspeed - Add HACE hash driver") Neal Liu
2022-08-29 10:47 ` Sudip Mukherjee
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=YwyORp72cuDrVYdA@debian \
--to=sudipm.mukherjee@gmail.com \
--cc=andrew@aj.id.au \
--cc=davem@davemloft.net \
--cc=dphadke@linux.microsoft.com \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=johnny_huang@aspeedtech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=neal_liu@aspeedtech.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