From: kernel test robot <lkp@intel.com>
To: Vinod Koul <vkoul@kernel.org>, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>, Rob Clark <robdclark@gmail.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
devicetree@vger.kernel.org,
Jernej Skrabec <jernej.skrabec@siol.net>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-arm-msm@vger.kernel.org, Jonas Karlman <jonas@kwiboo.se>,
Emil Velikov <emil.l.velikov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] drm/bridge: Introduce LT9611 DSI to HDMI bridge
Date: Thu, 11 Jun 2020 19:23:25 +0800 [thread overview]
Message-ID: <202006111945.TNhSwY0c%lkp@intel.com> (raw)
In-Reply-To: <20200611073611.1446562-4-vkoul@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
Hi Vinod,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master v5.7 next-20200611]
[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/Vinod-Koul/Add-LT9611-DSI-to-HDMI-bridge/20200611-153921
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: x86_64-allyesconfig (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project bc2b70982be8f5250cd0082a7190f8b417bd4dfe)
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 x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
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 <<):
>> make[5]: *** No rule to make target 'drivers/gpu/drm/bridge/lt9611.o', needed by 'drivers/gpu/drm/bridge/built-in.a'.
make[5]: Target '__build' not remade because of errors.
---
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: 73455 bytes --]
prev parent reply other threads:[~2020-06-11 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 7:36 [PATCH v2 0/3] Add " Vinod Koul
2020-06-11 7:36 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Lontium vendor prefix Vinod Koul
2020-06-11 7:36 ` [PATCH v2 2/3] dt-bindings: display: bridge: Add documentation for LT9611 Vinod Koul
2020-06-11 7:36 ` [PATCH v2 3/3] drm/bridge: Introduce LT9611 DSI to HDMI bridge Vinod Koul
2020-06-11 11:23 ` 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=202006111945.TNhSwY0c%lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@linux.ie \
--cc=clang-built-linux@googlegroups.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=emil.l.velikov@gmail.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robdclark@gmail.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®