Closed aafeijoo-suse closed 1 year ago
Do we need to wait to merge this? CONFIG_MICROCODE is set in the older kernels, so there should be no issue. Well, there is a scenario where someone on intel compiles the kernel with CONFIG_MICROCODE_AMD=y and CONFIG_MICROCODE_INTEL=n, but ... meh.
Do we need to wait to merge this? CONFIG_MICROCODE is set in the older kernels, so there should be no issue. Well, there is a scenario where someone on intel compiles the kernel with CONFIG_MICROCODE_AMD=y and CONFIG_MICROCODE_INTEL=n, but ... meh.
Ok, I agree.
FTR, already merged into master (https://github.com/torvalds/linux/commit/42a7f6e3ffe06308c1ec43a7dac39a27de101574), this patch will be required for 6.6-rc1.
CONFIG_MICROCODE_AMD
andCONFIG_MICROCODE_INTEL
are hidden since https://lore.kernel.org/all/20230810160805.081212701@linutronix.de/, therefore this check is wrong and early microcode is always disabled.Already merged into the tip tree, PR created as draft meanwhile it doesn't make it to the master branch.
Checklist