There are 14 Kconfig symbols referenced in the files used for
configuration generation and in the shipped .config files that were
dropped in upstream v5.5-rc1. The references to these symbols can be
safely removed.
These symbols are:
CONFIG_CALGARY_IOMMU
CONFIG_CRC_PMIC_OPREGION
CONFIG_CRYPTO_BLKCIPHER
CONFIG_HEADERS_CHECK
CONFIG_HEADER_TEST
CONFIG_INFINIBAND_CXGB3
CONFIG_INPUT_KXTJ9_POLLED_MODE
CONFIG_KERNEL_HEADER_TEST
CONFIG_PCIEASPM_DEBUG
CONFIG_PWM_TIPWMSS
CONFIG_QCOM_SDM845_LLCC
CONFIG_REFCOUNT_FULL
CONFIG_SIMPLE_GPIO
CONFIG_SND_HDA_INTEL_DETECT_DMIC
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Two Kconfig symbols were part of upstream v5.3-rc1 but didn't make it
into v5.3 (for reasons I couldn't be bothered to unearth): PREEMPT_LL
and SOUNDWIRE_BUS. Remove them from our configuration generation system
too.
Commit 3e636fe3a6 ("Remove patch for GCC VTA") forgot to clean up the
configs/ directory. Do so now.
Commit e21e52b608 ("Linux v5.3-13236-g97f9a3c4eee5") forgot to remove
CONFIG_LOCK_DOWN_KERNEL and CONFIG_LOCK_DOWN_KERNEL_FORCE from the
configs/ directory. Do so now.
Commit 5c0d4daff4 ("Remove crash driver") forgot to clean up the
configs/ directory. Do so now.
There are 22 Kconfig symbols referenced in the files used for
configuration generation and in the shipped .config files that were
dropped in upstream v5.4-rc1. The references to these symbols can be
safely removed.
These symbols are:
CONFIG_ARM_QCOM_CPUFREQ_KRYO
CONFIG_CRYPTO_AEGIS128L
CONFIG_CRYPTO_AEGIS128L_AESNI_SSE2
CONFIG_CRYPTO_AEGIS256
CONFIG_CRYPTO_AEGIS256_AESNI_SSE2
CONFIG_CRYPTO_AES_586
CONFIG_CRYPTO_AES_X86_64
CONFIG_CRYPTO_MORUS1280
CONFIG_CRYPTO_MORUS1280_AVX2
CONFIG_CRYPTO_MORUS1280_SSE2
CONFIG_CRYPTO_MORUS640
CONFIG_CRYPTO_MORUS640_SSE2
CONFIG_DRM_TINYDRM
CONFIG_HISI_KIRIN_DW_DSI
CONFIG_I2C_BCM2048
CONFIG_KEXEC_VERIFY_SIG
CONFIG_MFD_CROS_EC_CHARDEV
CONFIG_MTD_M25P80
CONFIG_SENSORS_ADS1015
CONFIG_SERIAL_8250_MOXA
CONFIG_SGI_IOC4
CONFIG_TINYDRM_MIPI_DBI
Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
This is a first pass at getting the secureboot patches working with the
upstream lockdown patches that got merged. The final patch from our
lockdown set is the sysrq patch which also needs work. For the present
it is not applied.
We've been carrying a patch to make CPUMASK_OFFSTACK selectable
without debugging for a long time now. The comment said this was
going to be replaced with something else but that never seemed
to happen. We're carrying it to have a higher number of CPUs but
at this point, adjusting NR_CPUS doesn't really get us that much
benfit. Drop the patch and just use 8192 or NR_CPUS on x86.
Signed-off-by: Laura Abbott <labbott@redhat.com>
Use the latest version of the kernel lockdown patch set. This includes a
few configuration renames:
CONFIG_KEXEC_VERIFY_SIG became CONFIG_KEXEC_SIG and
CONFIG_KEXEC_SIG_FORCE was added. CONFIG_KEXEC_SIG_FORCE=n because the
"kexec_file: Restrict at runtime if the kernel is locked down" patch
enforces the signature requirement when the kernel is locked down.
CONFIG_LOCK_DOWN_MANDATORY got renamed to CONFIG_LOCK_DOWN_KERNEL_FORCE
and remains false as LOCK_DOWN_IN_EFI_SECURE_BOOT covers enabling it for
EFI Secure Boot users.
Finally, the SysRq patches got dropped for the present.
