public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Loic Poulain <loic.poulain@linaro.org>,
	bjorn.andersson@linaro.org, agross@kernel.org
Cc: kbuild-all@lists.01.org, linux-arm-msm@vger.kernel.org,
	devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
	shawn.guo@linaro.org, Loic Poulain <loic.poulain@linaro.org>
Subject: Re: [PATCH 1/2] clk: qcom: Add display clock controller driver for QCM2290
Date: Thu, 9 Dec 2021 09:50:16 +0800	[thread overview]
Message-ID: <202112090948.3tbho958-lkp@intel.com> (raw)
In-Reply-To: <1638983841-23773-1-git-send-email-loic.poulain@linaro.org>

Hi Loic,

I love your patch! Yet something to improve:

[auto build test ERROR on clk/clk-next]
[also build test ERROR on v5.16-rc4 next-20211208]
[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/Loic-Poulain/clk-qcom-Add-display-clock-controller-driver-for-QCM2290/20211209-010708
base:   https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git clk-next
config: arc-allyesconfig (https://download.01.org/0day-ci/archive/20211209/202112090948.3tbho958-lkp@intel.com/config)
compiler: arceb-elf-gcc (GCC) 11.2.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/132fa9b498019a624b89dec6e53e34b480eb4be2
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Loic-Poulain/clk-qcom-Add-display-clock-controller-driver-for-QCM2290/20211209-010708
        git checkout 132fa9b498019a624b89dec6e53e34b480eb4be2
        # save the config file to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arc SHELL=/bin/bash

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 >>):

>> drivers/clk/qcom/dispcc-qcm2290.c:16:10: fatal error: dt-bindings/clock/qcom,dispcc-qcm2290.h: No such file or directory
      16 | #include <dt-bindings/clock/qcom,dispcc-qcm2290.h>
         |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   compilation terminated.


vim +16 drivers/clk/qcom/dispcc-qcm2290.c

    15	
  > 16	#include <dt-bindings/clock/qcom,dispcc-qcm2290.h>
    17	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

      parent reply	other threads:[~2021-12-09  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 17:17 [PATCH 1/2] clk: qcom: Add display clock controller driver for QCM2290 Loic Poulain
2021-12-08 17:17 ` [PATCH 2/2] dt-bindings: clock: Add qualcomm QCM2290 DISPCC bindings Loic Poulain
2021-12-08 23:06   ` Rob Herring
2021-12-09  1:50 ` kernel test robot [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=202112090948.3tbho958-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=loic.poulain@linaro.org \
    --cc=shawn.guo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox