Can you send me the configuration that created the warning ? It must have been in a allnoconfig mode, since the default of the menuconfig BLK_DEV is "y".
So looking at the x86_defconfig, while it doesn't have BLK_DEV enabled, it also doesn't have it explicitly disabled .. and hence BLK_DEV should have been on, and CONFIG_BLK_DEV_FD gone through to the final config. The patch is fine, and it isn't a bad thing to have the dependency explicitly in the fragment, I just want to understand the flow of fragments and the kconfig mode at play. Bruce In message: [linux-yocto] [kernel-cache][yocto-5.15][PATCH] cfg: fix x86_64 defconfig warnings on 21/01/2022 Naveen Saini wrote: > CONFIG_BLK_DEV_FD has dependeny on BLK_DEV, which is not enabled, as result > throws warning. > [NOTE]: 'CONFIG_BLK_DEV_FD' last val (m) and .config val (n) do not match > > Signed-off-by: Naveen Saini <[email protected]> > --- > bsp/common-pc/common-pc-drivers.cfg | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/bsp/common-pc/common-pc-drivers.cfg > b/bsp/common-pc/common-pc-drivers.cfg > index 7cb88817..e511c944 100644 > --- a/bsp/common-pc/common-pc-drivers.cfg > +++ b/bsp/common-pc/common-pc-drivers.cfg > @@ -55,6 +55,7 @@ CONFIG_I2C_I801=y > CONFIG_SATA_AHCI=y > > CONFIG_BLK_DEV_FD=m > +CONFIG_BLK_DEV=y > > CONFIG_EEPROM_AT24=m > > -- > 2.17.1 > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10860): https://lists.yoctoproject.org/g/linux-yocto/message/10860 Mute This Topic: https://lists.yoctoproject.org/mt/88579397/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/linux-yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
