From: kernel test robot <lkp@intel.com>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
robh+dt@kernel.org, devicetree@vger.kernel.org,
linux-arm-msm@vger.kernel.org, stanimir.varbanov@linaro.org,
agross@kernel.org, bjorn.andersson@linaro.org
Cc: kbuild-all@lists.01.org, bryan.odonoghue@linaro.org,
jonathan@marek.ca, dikshita@qti.qualcomm.com
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: sm8250: Add venus DT node
Date: Tue, 23 Feb 2021 03:45:24 +0800 [thread overview]
Message-ID: <202102230334.ryCxTagN-lkp@intel.com> (raw)
In-Reply-To: <20210222132817.1807788-4-bryan.odonoghue@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
Hi Bryan,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v5.11]
[cannot apply to next-20210222]
[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/0day-ci/linux/commits/Bryan-O-Donoghue/dts-qcom-sm8250-Enable-venus-related-DT-nodes/20210222-213330
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-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
# https://github.com/0day-ci/linux/commit/626c987912941b0f7bbf278824764ea53a5a13ad
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Bryan-O-Donoghue/dts-qcom-sm8250-Enable-venus-related-DT-nodes/20210222-213330
git checkout 626c987912941b0f7bbf278824764ea53a5a13ad
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
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 >>):
>> Error: arch/arm64/boot/dts/qcom/sm8250.dtsi:1827.16-17 syntax error
FATAL ERROR: Unable to parse 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: 76475 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 v2 3/3] arm64: dts: qcom: sm8250: Add venus DT node
Date: Tue, 23 Feb 2021 03:45:24 +0800 [thread overview]
Message-ID: <202102230334.ryCxTagN-lkp@intel.com> (raw)
In-Reply-To: <20210222132817.1807788-4-bryan.odonoghue@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Hi Bryan,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on v5.11]
[cannot apply to next-20210222]
[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/0day-ci/linux/commits/Bryan-O-Donoghue/dts-qcom-sm8250-Enable-venus-related-DT-nodes/20210222-213330
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: arm64-allyesconfig (attached as .config)
compiler: aarch64-linux-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
# https://github.com/0day-ci/linux/commit/626c987912941b0f7bbf278824764ea53a5a13ad
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Bryan-O-Donoghue/dts-qcom-sm8250-Enable-venus-related-DT-nodes/20210222-213330
git checkout 626c987912941b0f7bbf278824764ea53a5a13ad
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm64
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 >>):
>> Error: arch/arm64/boot/dts/qcom/sm8250.dtsi:1827.16-17 syntax error
FATAL ERROR: Unable to parse 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: 76475 bytes --]
next prev parent reply other threads:[~2021-02-22 19:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 13:28 [PATCH v2 0/3] dts: qcom: sm8250: Enable venus related DT nodes Bryan O'Donoghue
2021-02-22 13:28 ` [PATCH v2 1/3] arm64: dts: qcom: sm8250: add mmcx regulator Bryan O'Donoghue
2021-02-22 13:28 ` [PATCH v2 2/3] arm64: dts: qcom: sm8250: Add videocc DT node Bryan O'Donoghue
2021-02-22 13:28 ` [PATCH v2 3/3] arm64: dts: qcom: sm8250: Add venus " Bryan O'Donoghue
2021-02-22 19:45 ` kernel test robot [this message]
2021-02-22 19:45 ` kernel test robot
2021-02-22 21:17 ` kernel test robot
2021-02-22 21:17 ` kernel test robot
2021-02-22 21:39 ` Dmitry Baryshkov
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=202102230334.ryCxTagN-lkp@intel.com \
--to=lkp@intel.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=bryan.odonoghue@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dikshita@qti.qualcomm.com \
--cc=jonathan@marek.ca \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stanimir.varbanov@linaro.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 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.