From: kernel test robot <lkp@intel.com>
To: Anjelique Melendez <quic_amelende@quicinc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-leds@vger.kernel.org,
Lee Jones <lee@kernel.org>
Subject: [lee-leds:for-leds-next-next 48/56] drivers/leds/rgb/leds-qcom-lpg.c:17:10: fatal error: linux/soc/qcom/qcom-pbs.h: No such file or directory
Date: Sat, 13 Jan 2024 12:42:01 +0800 [thread overview]
Message-ID: <202401131235.zLTJE6Po-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/lee/leds.git for-leds-next-next
head: 1f88a09c35f8d50eff1adbc9e35cc2982b3ac9f9
commit: 07a1afc8fbb77cc893e2285112482902ac88a295 [48/56] leds: rgb: leds-qcom-lpg: Add support for PPG through single SDAM
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20240113/202401131235.zLTJE6Po-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240113/202401131235.zLTJE6Po-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/202401131235.zLTJE6Po-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/leds/rgb/leds-qcom-lpg.c:17:10: fatal error: linux/soc/qcom/qcom-pbs.h: No such file or directory
17 | #include <linux/soc/qcom/qcom-pbs.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +17 drivers/leds/rgb/leds-qcom-lpg.c
> 17 #include <linux/soc/qcom/qcom-pbs.h>
18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-13 4:42 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=202401131235.zLTJE6Po-lkp@intel.com \
--to=lkp@intel.com \
--cc=lee@kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_amelende@quicinc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox