Message ID | 20191121162322.671035-8-thomas.petazzoni@bootlin.com |
---|---|
State | Rejected, archived |
Headers | show |
Series | dm-verity support | expand |
diff --git a/config/Config-kernel.in b/config/Config-kernel.in index bdb6b91cbb..eae413eb29 100644 --- a/config/Config-kernel.in +++ b/config/Config-kernel.in @@ -860,3 +860,18 @@ config KERNEL_CC_OPTIMIZE_FOR_SIZE your compiler resulting in a smaller kernel. endchoice + +config KERNEL_MD + bool "Multiple devices driver support (RAID and LVM)" + +config KERNEL_BLK_DEV_DM + bool "Device mapper support" + depends on KERNEL_MD + +config KERNEL_DM_VERITY + bool "Verity target support" + depends on KERNEL_BLK_DEV_DM + +config KERNEL_DM_INIT + bool "DM \"dm-mod.create=\" parameter support" + depends on KERNEL_BLK_DEV_DM
The dm-verity support requires a number of kernel options to be enabled. This commit adds the corresponding options to config/Config-kernel.in, so that they can be selected by other OpenWrt options when needed. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> --- Note: I sometimes encounter an issue at build time where the kernel configuration system would prompt me for the values of the new options made visible as a result of enabling those MD, BLK_DEV_DM, DM_VERITY and DM_INIT options. Interestingly, I don't seem to encounter this at every build. I'm not sure why OpenWrt doesn't simply run a "make olddefconfig" to automatically accept the default values for unspecified options. What is the appropriate course of action to solve this problem ? --- config/Config-kernel.in | 15 +++++++++++++++ 1 file changed, 15 insertions(+)