From: Ard Biesheuvel <ardb@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: remove rmd320 in Makefile
Date: Mon, 16 Aug 2021 14:55:15 +0200 [thread overview]
Message-ID: <CAMj1kXFEGK_3RDXcO3kvCVQvOvoCLgRtQsR=pEbSaiY7erVJrQ@mail.gmail.com> (raw)
In-Reply-To: <20210816124433.10411-1-lukas.bulwahn@gmail.com>
On Mon, 16 Aug 2021 at 14:44, Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> Commit 93f64202926f ("crypto: rmd320 - remove RIPE-MD 320 hash algorithm")
> removes the Kconfig and code, but misses to adjust the Makefile.
>
> Hence, ./scripts/checkkconfigsymbols.py warns:
>
> CRYPTO_RMD320
> Referencing files: crypto/Makefile
>
> Remove the missing piece of this code removal.
>
> Fixes: 93f64202926f ("crypto: rmd320 - remove RIPE-MD 320 hash algorithm")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Acked-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> crypto/Makefile | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/crypto/Makefile b/crypto/Makefile
> index 10526d4559b8..c633f15a0481 100644
> --- a/crypto/Makefile
> +++ b/crypto/Makefile
> @@ -74,7 +74,6 @@ obj-$(CONFIG_CRYPTO_NULL2) += crypto_null.o
> obj-$(CONFIG_CRYPTO_MD4) += md4.o
> obj-$(CONFIG_CRYPTO_MD5) += md5.o
> obj-$(CONFIG_CRYPTO_RMD160) += rmd160.o
> -obj-$(CONFIG_CRYPTO_RMD320) += rmd320.o
> obj-$(CONFIG_CRYPTO_SHA1) += sha1_generic.o
> obj-$(CONFIG_CRYPTO_SHA256) += sha256_generic.o
> obj-$(CONFIG_CRYPTO_SHA512) += sha512_generic.o
> --
> 2.26.2
>
next prev parent reply other threads:[~2021-08-16 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 12:44 [PATCH] crypto: remove rmd320 in Makefile Lukas Bulwahn
2021-08-16 12:55 ` Ard Biesheuvel [this message]
2021-08-27 8:35 ` 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='CAMj1kXFEGK_3RDXcO3kvCVQvOvoCLgRtQsR=pEbSaiY7erVJrQ@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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).