From: kernel test robot <lkp@intel.com> To: Adam Ford <aford173@gmail.com>, linux-omap@vger.kernel.org Cc: kbuild-all@lists.01.org, aford@beaconembedded.com, "Adam Ford" <aford173@gmail.com>, "Benoît Cousson" <bcousson@baylibre.com>, "Tony Lindgren" <tony@atomide.com>, "Rob Herring" <robh+dt@kernel.org>, "Paul Walmsley" <paul@pwsan.com>, "Russell King" <linux@armlinux.org.uk>, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2 Date: Thu, 18 Jun 2020 01:26:39 +0800 [thread overview] Message-ID: <202006180107.6NIzI00f%lkp@intel.com> (raw) In-Reply-To: <20200617105840.22138-1-aford173@gmail.com> [-- Attachment #1: Type: text/plain, Size: 1543 bytes --] Hi Adam, Thank you for the patch! Yet something to improve: [auto build test ERROR on omap/for-next] [cannot apply to balbi-usb/testing/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Adam-Ford/ARM-dts-omap3-Migrate-AES-from-hwmods-to-sysc-omap2/20200617-190017 base: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git for-next config: arm-defconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 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 >>, old ones prefixed by <<): >> Error: arch/arm/boot/dts/omap3-tao3530.dtsi:11.1-5 Label or path aes not found >> FATAL ERROR: Syntax error parsing input tree -- >> Error: arch/arm/boot/dts/omap3-n900.dts:22.1-5 Label or path aes not found >> FATAL ERROR: Syntax error parsing input tree --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org [-- Attachment #2: .config.gz --] [-- Type: application/gzip, Size: 52040 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2 Date: Thu, 18 Jun 2020 01:26:39 +0800 [thread overview] Message-ID: <202006180107.6NIzI00f%lkp@intel.com> (raw) In-Reply-To: <20200617105840.22138-1-aford173@gmail.com> [-- Attachment #1: Type: text/plain, Size: 1579 bytes --] Hi Adam, Thank you for the patch! Yet something to improve: [auto build test ERROR on omap/for-next] [cannot apply to balbi-usb/testing/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982] url: https://github.com/0day-ci/linux/commits/Adam-Ford/ARM-dts-omap3-Migrate-AES-from-hwmods-to-sysc-omap2/20200617-190017 base: https://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git for-next config: arm-defconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (GCC) 9.3.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 # save the attached .config to linux build tree COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm 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 >>, old ones prefixed by <<): >> Error: arch/arm/boot/dts/omap3-tao3530.dtsi:11.1-5 Label or path aes not found >> FATAL ERROR: Syntax error parsing input tree -- >> Error: arch/arm/boot/dts/omap3-n900.dts:22.1-5 Label or path aes not found >> FATAL ERROR: Syntax error parsing input tree --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org [-- Attachment #2: config.gz --] [-- Type: application/gzip, Size: 52040 bytes --]
next prev parent reply other threads:[~2020-06-17 18:13 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-17 10:58 [PATCH] ARM: dts: omap3: Migrate AES from hwmods to sysc-omap2 Adam Ford 2020-06-17 10:58 ` Adam Ford 2020-06-17 17:26 ` kernel test robot [this message] 2020-06-17 17:26 ` kernel test robot 2020-06-29 18:12 ` Tony Lindgren 2020-06-29 18:12 ` Tony Lindgren 2020-06-30 0:29 ` [kbuild-all] " Rong Chen 2020-06-30 0:29 ` Rong Chen 2020-07-01 14:44 ` [kbuild-all] " Tony Lindgren 2020-07-01 14:44 ` Tony Lindgren -- strict thread matches above, loose matches on Subject: below -- 2020-05-04 23:01 Adam Ford 2020-05-04 23:01 ` Adam Ford 2020-05-05 18:42 ` Tony Lindgren 2020-05-05 18:42 ` Tony Lindgren 2020-05-05 21:17 ` Adam Ford 2020-05-05 21:17 ` Adam Ford 2020-05-05 23:34 ` Tony Lindgren 2020-05-05 23:34 ` Tony Lindgren 2020-06-13 11:10 ` Adam Ford 2020-06-13 11:10 ` Adam Ford 2020-06-13 15:50 ` Tony Lindgren 2020-06-13 15:50 ` Tony Lindgren
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=202006180107.6NIzI00f%lkp@intel.com \ --to=lkp@intel.com \ --cc=aford173@gmail.com \ --cc=aford@beaconembedded.com \ --cc=bcousson@baylibre.com \ --cc=devicetree@vger.kernel.org \ --cc=kbuild-all@lists.01.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-omap@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=paul@pwsan.com \ --cc=robh+dt@kernel.org \ --cc=tony@atomide.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: linkBe 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.