From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.6 217/217] cc1: warning: drivers/remoteproc/vcp: No such file or directory
Date: Tue, 11 Feb 2025 01:30:15 +0800 [thread overview]
Message-ID: <202502110137.W18F2RZp-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.6
head: b603fe68bcf1fd8aa46dd46190c53d641dce5cf0
commit: ea8227ece8dcae6cc6897798cac94b4aa2cf6a8c [217/217] CHROMIUM: soc: mediatek: add mtk-vdisp driver
config: arm-randconfig-002-20250210 (https://download.01.org/0day-ci/archive/20250211/202502110137.W18F2RZp-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250211/202502110137.W18F2RZp-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/202502110137.W18F2RZp-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> cc1: warning: drivers/remoteproc/vcp: No such file or directory [-Wmissing-include-dirs]
>> cc1: warning: drivers/remoteproc/vcp/include: No such file or directory [-Wmissing-include-dirs]
--
>> cc1: warning: drivers/remoteproc/vcp: No such file or directory [-Wmissing-include-dirs]
>> cc1: warning: drivers/remoteproc/vcp/include: No such file or directory [-Wmissing-include-dirs]
drivers/soc/mediatek/mtk-dvfsrc.c:139:5: warning: no previous prototype for 'dvfsrc_get_required_opp_peak_bw' [-Wmissing-prototypes]
139 | u32 dvfsrc_get_required_opp_peak_bw(struct device_node *np, int index)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-10 17:30 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=202502110137.W18F2RZp-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 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.