linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rong Chen <rong.a.chen@intel.com>
To: rojay@codeaurora.org, kernel test robot <lkp@intel.com>
Cc: agross@kernel.org, bjorn.andersson@linaro.org,
	robh+dt@kernel.org, kbuild-all@lists.01.org,
	clang-built-linux@googlegroups.com,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Rajendra Nayak <rnayak@codeaurora.org>,
	saiprakash.ranjan@codeaurora.org, msavaliy@qti.qualcomm.com
Subject: Re: [kbuild-all] Re: [PATCH V2] arm64: dts: sc7280: Add qspi, qupv3_0 and qupv3_1 nodes
Date: Tue, 25 May 2021 17:19:14 +0800	[thread overview]
Message-ID: <de30ea1c-5572-ca4e-e473-7b77724a90d8@intel.com> (raw)
In-Reply-To: <6950c9c7b54892b2a8e81915743431ea@codeaurora.org>



On 4/23/21 5:46 PM, rojay@codeaurora.org wrote:
> On 2021-04-23 02:52, kernel test robot wrote:
>> Hi Roja,
>>
>> Thank you for the patch! Yet something to improve:
>>
>> [auto build test ERROR on next-20210422]
>> [cannot apply to robh/for-next v5.12-rc8 v5.12-rc7 v5.12-rc6 v5.12-rc8]
>> [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/Roja-Rani-Yarubandi/arm64-dts-sc7280-Add-qspi-qupv3_0-and-qupv3_1-nodes/20210422-230756 
>>
>> base:    c457d9676496f5a895509f9c510278beaaffc829
>> config: arm64-randconfig-r012-20210421 (attached as .config)
>> compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project
>> f5446b769a7929806f72256fccd4826d66502e59)
>> 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
>>         # install arm64 cross compiling tool for clang build
>>         # apt-get install binutils-aarch64-linux-gnu
>>         #
>> https://github.com/0day-ci/linux/commit/78ed1b1d4c9f34dd06ae4494b78d70334fa8d7c1 
>>
>>         git remote add linux-review https://github.com/0day-ci/linux
>>         git fetch --no-tags linux-review
>> Roja-Rani-Yarubandi/arm64-dts-sc7280-Add-qspi-qupv3_0-and-qupv3_1-nodes/20210422-230756 
>>
>>         git checkout 78ed1b1d4c9f34dd06ae4494b78d70334fa8d7c1
>>         # save the attached .config to linux build tree
>>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1
>> 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/sc7280.dtsi:325.31-32 syntax error
>>    FATAL ERROR: Unable to parse input tree
>>
>
> This error is due to "clk_virt" node parse issue which will be defined 
> in ICC patches
> https://lore.kernel.org/patchwork/project/lkml/list/?series=488429
> I also mentioned the dependency in the patch.

Hi Roja,

Thanks for the clarification, we can parse the base commit from patch to 
avoid false positive:

     $ man git format-patch

          With git format-patch --base=P -3 C (or variants thereof, e.g. 
with --cover-letter or using Z..C instead of -3 C to specify the range), 
the base tree information block is shown at the end of the first message 
the command outputs (either the first patch, or the cover
        letter), like this:

            base-commit: P
            prerequisite-patch-id: X
            prerequisite-patch-id: Y
            prerequisite-patch-id: Z

Best Regards,
Rong Chen

      reply	other threads:[~2021-05-25  9:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 15:05 [PATCH V2] arm64: dts: sc7280: Add qspi, qupv3_0 and qupv3_1 nodes Roja Rani Yarubandi
2021-04-22 21:22 ` kernel test robot
2021-04-23  9:46   ` rojay
2021-05-25  9:19     ` Rong Chen [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=de30ea1c-5572-ca4e-e473-7b77724a90d8@intel.com \
    --to=rong.a.chen@intel.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=msavaliy@qti.qualcomm.com \
    --cc=rnayak@codeaurora.org \
    --cc=robh+dt@kernel.org \
    --cc=rojay@codeaurora.org \
    --cc=saiprakash.ranjan@codeaurora.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;
as well as URLs for NNTP newsgroup(s).