diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2020-06-10 14:05:13 +0300 |
---|---|---|
committer | Borislav Petkov <bp@suse.de> | 2020-06-15 12:59:19 +0300 |
commit | c8a59a4d8e3c9e609fa915e39c3628c6dd08aeea (patch) | |
tree | 72e9bd7a4ae54215415c53f9b115db34d61f1ddd /arch/arm/crypto/sha256-armv4.pl | |
parent | b3a9e3b9622ae10064826dccb4f7a52bd88c7407 (diff) | |
download | linux-c8a59a4d8e3c9e609fa915e39c3628c6dd08aeea.tar.xz |
x86/microcode: Do not select FW_LOADER
The x86 microcode support works just fine without FW_LOADER. In fact,
these days most people load microcode early during boot so FW_LOADER
never gets into the picture anyway.
As almost everyone on x86 needs to enable MICROCODE, this by extension
means that FW_LOADER is always built into the kernel even if nothing
uses it. The FW_LOADER system is about two thousand lines long and
contains user-space facing interfaces that could potentially provide an
entry point into the kernel (or beyond).
Remove the unnecessary select of FW_LOADER by MICROCODE. People who need
the FW_LOADER capability can still enable it.
[ bp: Massage a bit. ]
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Borislav Petkov <bp@suse.de>
Link: https://lkml.kernel.org/r/20200610042911.GA20058@gondor.apana.org.au
Diffstat (limited to 'arch/arm/crypto/sha256-armv4.pl')
0 files changed, 0 insertions, 0 deletions