From: kernel test robot <lkp@intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: kbuild-all@lists.01.org, Biju Das <biju.das.jz@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-renesas-soc@vger.kernel.org, linux-clk@vger.kernel.org,
Chris Paterson <Chris.Paterson2@renesas.com>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v5 1/3] clk: renesas: Add support for RZ/G2UL SoC
Date: Wed, 13 Apr 2022 05:05:12 +0800 [thread overview]
Message-ID: <202204130437.n3GTbhuH-lkp@intel.com> (raw)
In-Reply-To: <20220412161314.13800-2-biju.das.jz@bp.renesas.com>
Hi Biju,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on geert-renesas-drivers/renesas-clk]
[also build test ERROR on geert-renesas-devel/next krzk/for-next v5.18-rc2 next-20220412]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/intel-lab-lkp/linux/commits/Biju-Das/Add-Renesas-RZ-G2UL-Type-1-SoC-SMARC-EVK-support/20220413-003233
base: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers.git renesas-clk
config: nios2-allyesconfig (https://download.01.org/0day-ci/archive/20220413/202204130437.n3GTbhuH-lkp@intel.com/config)
compiler: nios2-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/ecfc4ccb6c8bc2ea667b9387be29a4b96212499d
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Biju-Das/Add-Renesas-RZ-G2UL-Type-1-SoC-SMARC-EVK-support/20220413-003233
git checkout ecfc4ccb6c8bc2ea667b9387be29a4b96212499d
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=nios2 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/renesas/r9a07g043-cpg.c:13:10: fatal error: dt-bindings/clock/r9a07g043-cpg.h: No such file or directory
13 | #include <dt-bindings/clock/r9a07g043-cpg.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +13 drivers/clk/renesas/r9a07g043-cpg.c
12
> 13 #include <dt-bindings/clock/r9a07g043-cpg.h>
14
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-04-12 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220412161314.13800-1-biju.das.jz@bp.renesas.com>
2022-04-12 16:13 ` [PATCH v5 1/3] clk: renesas: Add support for RZ/G2UL SoC Biju Das
2022-04-12 21:05 ` kernel test robot [this message]
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=202204130437.n3GTbhuH-lkp@intel.com \
--to=lkp@intel.com \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=geert+renesas@glider.be \
--cc=kbuild-all@lists.01.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=sboyd@kernel.org \
/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