On Mon, 1 Sept 2025 at 22:29, Eric Biggers <ebigg...@kernel.org> wrote:
> Currently, Curve25519 has both a library API and a crypto_kpp API.
> However, the crypto_kpp API to Curve25519 has no users outside
> crypto/testmgr.c. I.e., no non-test code ever passes "curve25519" to
> crypto_alloc_kpp(). And the crypto/testmgr.c test coverage for
> Curve25519 isn't particularly useful either, since it just runs the same
> list of test vectors that curve25519-selftest uses.
>
> Therefore, all the crypto_kpp support for Curve25519 is unnecessary.
>
> Remove it. We'll instead focus on the Curve25519 library API, which is
> the API that is actually being used. Curve25519 remains fully supported
> for in-kernel users via the library API (crypto/curve25519.h).
>
> Signed-off-by: Eric Biggers <ebigg...@kernel.org>
> arch/m68k/configs/amiga_defconfig | 1 -
> arch/m68k/configs/apollo_defconfig | 1 -
> arch/m68k/configs/atari_defconfig | 1 -
> arch/m68k/configs/bvme6000_defconfig | 1 -
> arch/m68k/configs/hp300_defconfig | 1 -
> arch/m68k/configs/mac_defconfig | 1 -
> arch/m68k/configs/multi_defconfig | 1 -
> arch/m68k/configs/mvme147_defconfig | 1 -
> arch/m68k/configs/mvme16x_defconfig | 1 -
> arch/m68k/configs/q40_defconfig | 1 -
> arch/m68k/configs/sun3_defconfig | 1 -
> arch/m68k/configs/sun3x_defconfig | 1 -
Acked-by: Geert Uytterhoeven <ge...@linux-m68k.org> # m68k
(although this would be handled during the regular defconfig refresh anyway)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
