From: kernel test robot <lkp@intel.com>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: "Paul Gazzillo" <paul@pgazz.com>,
"Necip Fazil Yildiran" <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Ciju Rajan K" <crajank@nvidia.com>
Subject: [pdx86-platform-drivers-x86:review-ilpo-next 55/58] kismet: WARNING: unmet direct dependencies detected for REGMAP_I2C when selected by MLXREG_DPU
Date: Tue, 29 Apr 2025 22:12:48 +0800 [thread overview]
Message-ID: <202504292201.JSFwvIMC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git review-ilpo-next
head: f618f1b298d3195d363b20f158ccb3facf553f0d
commit: 3e75f295411679e999dbcca37499cd00bd643060 [55/58] platform/mellanox: mlxreg-dpu: Add initial support for Nvidia DPU
config: nios2-kismet-CONFIG_REGMAP_I2C-CONFIG_MLXREG_DPU-0-0 (https://download.01.org/0day-ci/archive/20250429/202504292201.JSFwvIMC-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20250429/202504292201.JSFwvIMC-lkp@intel.com/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@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202504292201.JSFwvIMC-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for REGMAP_I2C when selected by MLXREG_DPU
WARNING: unmet direct dependencies detected for REGMAP_I2C
Depends on [n]: I2C [=n]
Selected by [y]:
- MLXREG_DPU [=y] && MELLANOX_PLATFORM [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-29 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202504292201.JSFwvIMC-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=crajank@nvidia.com \
--cc=fazilyildiran@gmail.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=vadimp@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.