From: kernel test robot <lkp@intel.com>
To: kostap@marvell.com, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kbuild-all@lists.01.org, lkundrak@v3.sk, linux@armlinux.org.uk,
sebastian.hesselbarth@gmail.com, gregory.clement@bootlin.com,
andrew@lunn.ch, robh+dt@kernel.org, vkoul@kernel.org
Subject: Re: [PATCH v2 1/4] drivers: phy: add support for Armada CP110 UTMI PHY
Date: Sun, 21 Feb 2021 21:12:11 +0800 [thread overview]
Message-ID: <202102212101.FrCNrTDb-lkp@intel.com> (raw)
In-Reply-To: <20210214160108.3879-2-kostap@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 1812 bytes --]
Hi,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on arm/for-next keystone/next soc/for-next rockchip/for-next arm64/for-next/core shawnguo/for-next kvmarm/next linus/master v5.11]
[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/kostap-marvell-com/Add-support-for-CP110-UTMI-PHY/20210215-000633
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
config: parisc-randconfig-r034-20210221 (attached as .config)
compiler: hppa-linux-gcc (GCC) 9.3.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/dcbc3ab68fea9223d2fe44c3348da8a11c9d5ce3
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review kostap-marvell-com/Add-support-for-CP110-UTMI-PHY/20210215-000633
git checkout dcbc3ab68fea9223d2fe44c3348da8a11c9d5ce3
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=parisc
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 >>):
hppa-linux-ld: drivers/phy/marvell/phy-mvebu-cp110-utmi.o: in function `mvebu_cp110_utmi_phy_probe':
>> (.text+0x230): undefined reference to `of_usb_get_dr_mode_by_phy'
---
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: 34086 bytes --]
next prev parent reply other threads:[~2021-02-21 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 16:01 [PATCH v2 0/4] Add support for CP110 UTMI PHY kostap
2021-02-14 16:01 ` [PATCH v2 1/4] drivers: phy: add support for Armada " kostap
2021-02-21 13:12 ` kernel test robot [this message]
2021-02-21 13:23 ` kernel test robot
2021-02-14 16:01 ` [PATCH v2 2/4] devicetree/bindings: add support for CP110 UTMI driver kostap
2021-03-05 21:34 ` Rob Herring
2021-02-14 16:01 ` [PATCH v2 3/4] arch/arm64: dts: add support for Marvell " kostap
2021-02-14 16:01 ` [PATCH v2 4/4] arch/arm64: dts: enable " kostap
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=202102212101.FrCNrTDb-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=kbuild-all@lists.01.org \
--cc=kostap@marvell.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lkundrak@v3.sk \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@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;
as well as URLs for NNTP newsgroup(s).