From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Subject: Re: [PATCH v16 8/8] ARM: dts: imx7d: remarkable2: Enable lcdif
Date: Sun, 05 Dec 2021 22:26:05 +0800 [thread overview]
Message-ID: <202112052123.Q9Dgewcq-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
CC: kbuild-all(a)lists.01.org
In-Reply-To: <20211202120758.41478-9-alistair@alistair23.me>
References: <20211202120758.41478-9-alistair@alistair23.me>
TO: Alistair Francis <alistair@alistair23.me>
TO: kernel(a)pengutronix.de
TO: robh+dt(a)kernel.org
TO: lee.jones(a)linaro.org
TO: lgirdwood(a)gmail.com
TO: broonie(a)kernel.org
CC: linux-arm-kernel(a)lists.infradead.org
CC: alistair23(a)gmail.com
CC: linux-hwmon(a)vger.kernel.org
CC: andreas(a)kemnade.info
CC: s.hauer(a)pengutronix.de
Hi Alistair,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on lee-mfd/for-mfd-next robh/for-next v5.16-rc3 next-20211203]
[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/Alistair-Francis/Add-support-for-the-silergy-sy7636a/20211202-201116
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce: make ARCH=arm dtbs_check
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
dtcheck warnings: (new ones prefixed by >>)
make[2]: *** [scripts/Makefile.lib:346: arch/arm/boot/dts/imx7d-remarkable2.dtb] Error 1
>> make[2]: *** [scripts/Makefile.lib:373: arch/arm/boot/dts/imx7d-remarkable2.dt.yaml] Error 1
make[2]: Target '__build' not remade because of errors.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
next reply other threads:[~2021-12-05 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 14:26 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-02 12:07 [PATCH v16 0/8] Add support for the silergy,sy7636a Alistair Francis
2021-12-02 12:07 ` [PATCH v16 8/8] ARM: dts: imx7d: remarkable2: Enable lcdif Alistair Francis
2021-12-02 12:07 ` Alistair Francis
2021-12-05 1:22 ` kernel test robot
2021-12-05 1:22 ` kernel test robot
2021-12-05 1:22 ` kernel test robot
2021-12-05 5:37 ` kernel test robot
2021-12-05 5:37 ` kernel test robot
2021-12-05 5:37 ` kernel test robot
2021-12-05 21:07 ` Andreas Kemnade
2021-12-05 21:07 ` Andreas Kemnade
2021-12-06 12:51 ` Alistair Francis
2021-12-06 12:51 ` Alistair Francis
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=202112052123.Q9Dgewcq-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild@lists.01.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.