On Sat, Jun 29, 2024 at 10:14:59AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: 1eb586a9782cde8e5091b9de74603e0a8386b09e > commit: 218ae84503fff008005ef4525f5b13fe0080ab4b [8598/9689] arm64: dts: imx8qm-mek: add cm4 remote-proc and related memory region > config: arm64-randconfig-r013-20211027 > compiler: aarch64-linux-gcc (GCC) 13.2.0 > reproduce (this is a W=1 build): > > 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@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202406290945.3KbIuqTZ-lkp@xxxxxxxxx/ > > dtcheck warnings: (new ones prefixed by >>) > >> arch/arm64/boot/dts/freescale/imx8qm-mek.dts:64.22-68.5: Warning (unit_address_vs_reg): /reserved-memory/memory: node has a reg or ranges property, but no unit name Fixed it up with the change below. diff --git a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts index 4a6f47f0998c..08c35a1ee73e 100644 --- a/arch/arm64/boot/dts/freescale/imx8qm-mek.dts +++ b/arch/arm64/boot/dts/freescale/imx8qm-mek.dts @@ -61,7 +61,7 @@ rsc_table0: memory@900ff000 { no-map; }; - vdevbuffer: memory { + vdevbuffer: memory@90400000 { compatible = "shared-dma-pool"; reg = <0 0x90400000 0 0x100000>; no-map;
