From: kernel test robot <lkp@intel.com>
To: Adam Ford <aford173@gmail.com>, linux-arm-kernel@lists.infradead.org
Cc: Fabio Estevam <festevam@gmail.com>,
kbuild-all@lists.01.org, Stephen Boyd <sboyd@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
NXP Linux Team <linux-imx@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fugang Duan <fugang.duan@nxp.com>, Adam Ford <aford173@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/2] clk: imx: enable the earlycon uart clocks by parsing from dt
Date: Wed, 30 Dec 2020 23:45:16 +0800 [thread overview]
Message-ID: <202012302317.Vw4Svoey-lkp@intel.com> (raw)
In-Reply-To: <20201229145130.2680442-1-aford173@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1569 bytes --]
Hi Adam,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on clk/clk-next rockchip/for-next soc/for-next v5.11-rc1 next-20201223]
[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/Adam-Ford/clk-imx-enable-the-earlycon-uart-clocks-by-parsing-from-dt/20201229-225330
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
config: i386-randconfig-a016-20201230 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/dbc1139f0f9718caba0f0091cdf3ece65ef47f3f
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Adam-Ford/clk-imx-enable-the-earlycon-uart-clocks-by-parsing-from-dt/20201229-225330
git checkout dbc1139f0f9718caba0f0091cdf3ece65ef47f3f
# save the attached .config to linux build tree
make W=1 ARCH=i386
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 >>):
ld: drivers/clk/imx/clk.o: in function `imx_earlycon_uart_clks_onoff':
>> clk.c:(.text+0x1bd): undefined reference to `of_stdout'
---
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: 36190 bytes --]
[-- Attachment #3: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-12-30 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 14:51 [PATCH 1/2] clk: imx: enable the earlycon uart clocks by parsing from dt Adam Ford
2020-12-29 14:51 ` [PATCH 2/2] clk: imx: Cleanup references to imx_register_uart_clocks Adam Ford
2020-12-30 15:45 ` kernel test robot [this message]
2021-01-04 7:11 ` [PATCH 1/2] clk: imx: enable the earlycon uart clocks by parsing from dt Sascha Hauer
2021-01-10 16:56 ` Adam Ford
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=202012302317.Vw4Svoey-lkp@intel.com \
--to=lkp@intel.com \
--cc=aford173@gmail.com \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=kbuild-all@lists.01.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mturquette@baylibre.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).