[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877d4aeg4t.fsf@mpe.ellerman.id.au>
Date: Mon, 18 Jul 2022 22:53:38 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: "Jason A. Donenfeld" <Jason@...c4.com>,
Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
linux-arm-kernel@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org, linux-s390@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Heiko Carstens <hca@...ux.ibm.com>,
Alexander Gordeev <agordeev@...ux.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Arnd Bergmann <arnd@...db.de>, Borislav Petkov <bp@...e.de>
Cc: "Jason A. Donenfeld" <Jason@...c4.com>
Subject: Re: [PATCH v5] random: remove CONFIG_ARCH_RANDOM
"Jason A. Donenfeld" <Jason@...c4.com> writes:
> When RDRAND was introduced, there was much discussion on whether it
> should be trusted and how the kernel should handle that. Initially, two
> mechanisms cropped up, CONFIG_ARCH_RANDOM, a compile time switch, and
> "nordrand", a boot-time switch.
...
>
> arch/arm/include/asm/archrandom.h | 2 ++
> arch/arm64/Kconfig | 8 ------
> arch/arm64/include/asm/archrandom.h | 10 --------
> arch/arm64/kernel/cpufeature.c | 2 --
> arch/powerpc/Kconfig | 3 ---
> arch/powerpc/include/asm/archrandom.h | 3 ---
> arch/powerpc/include/asm/machdep.h | 2 --
> arch/powerpc/platforms/microwatt/Kconfig | 1 -
> arch/powerpc/platforms/powernv/Kconfig | 1 -
> arch/powerpc/platforms/pseries/Kconfig | 1 -
Acked-by: Michael Ellerman <mpe@...erman.id.au> (powerpc)
cheers
Powered by blists - more mailing lists