From: kernel test robot <lkp@intel.com>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-leds@vger.kernel.org, Lee Jones <lee@kernel.org>
Subject: [lee-leds:for-leds-next 21/28] drivers/leds/rgb/leds-s2m-rgb.c:12:10: fatal error: 'linux/mfd/samsung/s2mu005.h' file not found
Date: Sat, 06 Jun 2026 00:04:32 +0800 [thread overview]
Message-ID: <202606052337.5WHsvu5q-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next
head: a2263676302a4eec40af93b3829f1d3d5aade93c
commit: 366ed7a6d22e682e6dfd4d64d8f543bc70c6b58e [21/28] leds: rgb: Add support for Samsung S2M series PMIC RGB LED device
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260605/202606052337.5WHsvu5q-lkp@intel.com/config)
compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260605/202606052337.5WHsvu5q-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/202606052337.5WHsvu5q-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/leds/rgb/leds-s2m-rgb.c:12:10: fatal error: 'linux/mfd/samsung/s2mu005.h' file not found
12 | #include <linux/mfd/samsung/s2mu005.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +12 drivers/leds/rgb/leds-s2m-rgb.c
> 12 #include <linux/mfd/samsung/s2mu005.h>
13 #include <linux/minmax.h>
14 #include <linux/module.h>
15 #include <linux/mutex.h>
16 #include <linux/of.h>
17 #include <linux/platform_device.h>
18 #include <linux/regmap.h>
19
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-05 16:04 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=202606052337.5WHsvu5q-lkp@intel.com \
--to=lkp@intel.com \
--cc=kauschluss@disroot.org \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox