From: kernel test robot <lkp@intel.com>
To: Biju Das <biju.das.jz@bp.renesas.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH 1/2] arm64: dts: renesas: r9a09g047: Add XSPI node
Date: Fri, 9 May 2025 16:42:50 +0800 [thread overview]
Message-ID: <202505091649.PuAhqb0T-lkp@intel.com> (raw)
In-Reply-To: <20250508183109.137721-2-biju.das.jz@bp.renesas.com>
Hi Biju,
kernel test robot noticed the following build errors:
[auto build test ERROR on geert-renesas-devel/next]
[also build test ERROR on linus/master v6.15-rc5 next-20250508]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Biju-Das/arm64-dts-renesas-r9a09g047-Add-XSPI-node/20250509-023503
base: https://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next
patch link: https://lore.kernel.org/r/20250508183109.137721-2-biju.das.jz%40bp.renesas.com
patch subject: [PATCH 1/2] arm64: dts: renesas: r9a09g047: Add XSPI node
config: arm64-randconfig-001-20250509 (https://download.01.org/0day-ci/archive/20250509/202505091649.PuAhqb0T-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505091649.PuAhqb0T-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/202505091649.PuAhqb0T-lkp@intel.com/
All errors (new ones prefixed by >>):
>> Error: arch/arm64/boot/dts/renesas/r9a09g047.dtsi:293.14-15 syntax error
FATAL ERROR: Unable to parse input tree
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-09 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 18:31 [PATCH 0/2] Enable serial NOR flash on RZ/G3E SMARC EVK Biju Das
2025-05-08 18:31 ` [PATCH 1/2] arm64: dts: renesas: r9a09g047: Add XSPI node Biju Das
2025-05-09 8:42 ` kernel test robot [this message]
2025-05-09 8:57 ` Biju Das
2025-05-09 12:07 ` Philip Li
2025-05-21 9:41 ` Geert Uytterhoeven
2025-05-08 18:31 ` [PATCH 2/2] arm64: dts: renesas: rzg3e-smarc-som: Enable serial nor flash Biju Das
2025-05-21 9:43 ` Geert Uytterhoeven
2025-05-08 18:37 ` [PATCH 0/2] Enable serial NOR flash on RZ/G3E SMARC EVK Biju Das
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=202505091649.PuAhqb0T-lkp@intel.com \
--to=lkp@intel.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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