Doing experimental build of linux-rpi
, it looks like the upstream changes were adopted:
$ find -name bcm\*defconfig |ack -x DM_INTEGRITY
./src/linux-6.1/arch/arm/configs/bcm2709_defconfig
480:CONFIG_DM_INTEGRITY=m
./src/linux-6.1/arch/arm/configs/bcmrpi_defconfig
475:CONFIG_DM_INTEGRITY=m
./src/linux-6.1/arch/arm/configs/bcm2711_defconfig
492:CONFIG_DM_INTEGRITY=m
./src/linux-6.1/arch/arm64/configs/bcmrpi3_defconfig
477:CONFIG_DM_INTEGRITY=m
./src/linux-6.1/arch/arm64/configs/bcm2711_defconfig
496:CONFIG_DM_INTEGRITY=m
Upstream pull request was merged, shall we do anything here? Or close this?
Btw, how long does it usually take for such upstream changes to be adopted?
I created https://github.com/raspberrypi/linux/pull/5337, let's see what upstream thinks. Feel free to check it and pinpoint any possible mistakes I did.
Sure, but I am very new to the process. Should I add it to all flavors mentioned in APKBUILD
? Meaning:
bcmrpi_defconfig
bcmrpi3_defconfig
bcm2709_defconfig
bcm2711_defconfig
Or just a specific one I need (I am interested in RPi 4 aarch64, so probably bcm2711_defconfig
)?
Stanislav Židek (09731c4b) at 22 Jan 12:23
main/linux-rpi: added CONFIG_DM_INTEGRITY=m
... and 1 more commit
Stanislav Židek (882b2064) at 22 Jan 11:16
main/linux-rpi: added CONFIG_DM_INTEGRITY=m