From: kernel test robot <lkp@intel.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: Paul Gazzillo <paul@pgazz.com>,
Necip Fazil Yildiran <fazilyildiran@gmail.com>,
oe-kbuild-all@lists.linux.dev,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [linux-next:master 12363/13990] kismet: WARNING: unmet direct dependencies detected for CAN_DEV when selected by CAN
Date: Tue, 9 Dec 2025 15:29:51 +0100 [thread overview]
Message-ID: <202512091523.zty3CLmc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: c75caf76ed86bbc15a72808f48f8df1608a0886c
commit: cb2dc6d2869a4fb7ef8d792a81a74bc6f0958a72 [12363/13990] can: Kconfig: select CAN driver infrastructure by default
config: loongarch-kismet-CONFIG_CAN_DEV-CONFIG_CAN-0-0 (https://download.01.org/0day-ci/archive/20251209/202512091523.zty3CLmc-lkp@intel.com/config)
reproduce: (https://download.01.org/0day-ci/archive/20251209/202512091523.zty3CLmc-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/202512091523.zty3CLmc-lkp@intel.com/
kismet warnings: (new ones prefixed by >>)
>> kismet: WARNING: unmet direct dependencies detected for CAN_DEV when selected by CAN
WARNING: unmet direct dependencies detected for CAN_DEV
Depends on [n]: NETDEVICES [=n] && CAN [=y]
Selected by [y]:
- CAN [=y] && NET [=y]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-12-09 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 14:29 kernel test robot [this message]
2025-12-09 16:02 ` [linux-next:master 12363/13990] kismet: WARNING: unmet direct dependencies detected for CAN_DEV when selected by CAN Oliver Hartkopp
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=202512091523.zty3CLmc-lkp@intel.com \
--to=lkp@intel.com \
--cc=fazilyildiran@gmail.com \
--cc=mkl@pengutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paul@pgazz.com \
--cc=socketcan@hartkopp.net \
/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.