On Sat, Sep 7, 2024 at 10:27 AM kernel test robot <lkp@xxxxxxxxx> wrote: > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-unstable > head: e8d9739d326fade1f58bc90726d2f9ebe35ae708 > commit: 4f6a358be27cd25e5e808031cc1715c2b6a0ef6f [149/155] mm: z3fold: deprecate CONFIG_Z3FOLD > config: x86_64-kismet-CONFIG_Z3FOLD-CONFIG_ZSWAP_ZPOOL_DEFAULT_Z3FOLD-0-0 (https://download.01.org/0day-ci/archive/20240908/202409080151.fMmh2yu4-lkp@xxxxxxxxx/config) > reproduce: (https://download.01.org/0day-ci/archive/20240908/202409080151.fMmh2yu4-lkp@xxxxxxxxx/reproduce) > > If you fix the issue in a separate patch/commit (i.e. not just a new version of > the same patch/commit), kindly add following tags > | Reported-by: kernel test robot <lkp@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202409080151.fMmh2yu4-lkp@xxxxxxxxx/ > > kismet warnings: (new ones prefixed by >>) > >> kismet: WARNING: unmet direct dependencies detected for Z3FOLD when selected by ZSWAP_ZPOOL_DEFAULT_Z3FOLD > WARNING: unmet direct dependencies detected for Z3FOLD > Depends on [n]: Z3FOLD_DEPRECATED [=n] > Selected by [y]: > - ZSWAP_ZPOOL_DEFAULT_Z3FOLD [=y] && ZSWAP [=y] This seems to be working as intended, we cannot enable CONFIG_ ZSWAP_ZPOOL_DEFAULT_Z3FOLD unless CONFIG_ Z3FOLD_DEPRECATED is explicitly enabled. Maybe this isn't the correct way to do it? Should I make CONFIG_ ZSWAP_ZPOOL_DEFAULT_Z3FOLD depend on CONFIG_Z3FOLD instead of selecting it? > > -- > 0-DAY CI Kernel Test Service > https://github.com/intel/lkp-tests/wiki
