From: kernel test robot <lkp@intel.com>
To: Colin Foster <colin.foster@in-advantage.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH v1 net-next 5/6] net: mscc: ocelot: split register definitions to a separate file
Date: Sat, 20 Nov 2021 11:23:11 +0800 [thread overview]
Message-ID: <202111201126.brIbRWKN-lkp@intel.com> (raw)
In-Reply-To: <20211119224313.2803941-6-colin.foster@in-advantage.com>
[-- Attachment #1: Type: text/plain, Size: 6025 bytes --]
Hi Colin,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Colin-Foster/prepare-ocelot-for-external-interface-control/20211120-064530
base: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git 520fbdf7fb19b7744e370d36d9244a446299ceb7
config: i386-randconfig-a002-20211118 (attached as .config)
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/a5f13354942bd393fe1014a9c1b3d34dd8ec5f52
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Colin-Foster/prepare-ocelot-for-external-interface-control/20211120-064530
git checkout a5f13354942bd393fe1014a9c1b3d34dd8ec5f52
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/net/ethernet/mscc/
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/net/ethernet/mscc/ocelot_vsc7514.c:28:10: error: use of undeclared identifier 'vsc7514_ana_regmap'; did you mean 'ocelot_ana_regmap'?
[ANA] = vsc7514_ana_regmap,
^~~~~~~~~~~~~~~~~~
ocelot_ana_regmap
include/soc/mscc/vsc7514_regs.h:11:18: note: 'ocelot_ana_regmap' declared here
extern const u32 ocelot_ana_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:29:9: error: use of undeclared identifier 'vsc7514_qs_regmap'; did you mean 'ocelot_qs_regmap'?
[QS] = vsc7514_qs_regmap,
^~~~~~~~~~~~~~~~~
ocelot_qs_regmap
include/soc/mscc/vsc7514_regs.h:12:18: note: 'ocelot_qs_regmap' declared here
extern const u32 ocelot_qs_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:30:11: error: use of undeclared identifier 'vsc7514_qsys_regmap'; did you mean 'ocelot_qsys_regmap'?
[QSYS] = vsc7514_qsys_regmap,
^~~~~~~~~~~~~~~~~~~
ocelot_qsys_regmap
include/soc/mscc/vsc7514_regs.h:13:18: note: 'ocelot_qsys_regmap' declared here
extern const u32 ocelot_qsys_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:31:10: error: use of undeclared identifier 'vsc7514_rew_regmap'; did you mean 'ocelot_rew_regmap'?
[REW] = vsc7514_rew_regmap,
^~~~~~~~~~~~~~~~~~
ocelot_rew_regmap
include/soc/mscc/vsc7514_regs.h:14:18: note: 'ocelot_rew_regmap' declared here
extern const u32 ocelot_rew_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:32:10: error: use of undeclared identifier 'vsc7514_sys_regmap'; did you mean 'ocelot_sys_regmap'?
[SYS] = vsc7514_sys_regmap,
^~~~~~~~~~~~~~~~~~
ocelot_sys_regmap
include/soc/mscc/vsc7514_regs.h:15:18: note: 'ocelot_sys_regmap' declared here
extern const u32 ocelot_sys_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:33:9: error: use of undeclared identifier 'vsc7514_vcap_regmap'; did you mean 'ocelot_vcap_regmap'?
[S0] = vsc7514_vcap_regmap,
^~~~~~~~~~~~~~~~~~~
ocelot_vcap_regmap
include/soc/mscc/vsc7514_regs.h:16:18: note: 'ocelot_vcap_regmap' declared here
extern const u32 ocelot_vcap_regmap[];
^
drivers/net/ethernet/mscc/ocelot_vsc7514.c:34:9: error: use of undeclared identifier 'vsc7514_vcap_regmap'; did you mean 'ocelot_vcap_regmap'?
[S1] = vsc7514_vcap_regmap,
^~~~~~~~~~~~~~~~~~~
ocelot_vcap_regmap
include/soc/mscc/vsc7514_regs.h:16:18: note: 'ocelot_vcap_regmap' declared here
extern const u32 ocelot_vcap_regmap[];
^
drivers/net/ethernet/mscc/ocelot_vsc7514.c:35:9: error: use of undeclared identifier 'vsc7514_vcap_regmap'; did you mean 'ocelot_vcap_regmap'?
[S2] = vsc7514_vcap_regmap,
^~~~~~~~~~~~~~~~~~~
ocelot_vcap_regmap
include/soc/mscc/vsc7514_regs.h:16:18: note: 'ocelot_vcap_regmap' declared here
extern const u32 ocelot_vcap_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:36:10: error: use of undeclared identifier 'vsc7514_ptp_regmap'; did you mean 'ocelot_ptp_regmap'?
[PTP] = vsc7514_ptp_regmap,
^~~~~~~~~~~~~~~~~~
ocelot_ptp_regmap
include/soc/mscc/vsc7514_regs.h:17:18: note: 'ocelot_ptp_regmap' declared here
extern const u32 ocelot_ptp_regmap[];
^
>> drivers/net/ethernet/mscc/ocelot_vsc7514.c:37:15: error: use of undeclared identifier 'vsc7514_dev_gmii_regmap'; did you mean 'ocelot_dev_gmii_regmap'?
[DEV_GMII] = vsc7514_dev_gmii_regmap,
^~~~~~~~~~~~~~~~~~~~~~~
ocelot_dev_gmii_regmap
include/soc/mscc/vsc7514_regs.h:18:18: note: 'ocelot_dev_gmii_regmap' declared here
extern const u32 ocelot_dev_gmii_regmap[];
^
10 errors generated.
vim +28 drivers/net/ethernet/mscc/ocelot_vsc7514.c
26
27 static const u32 *ocelot_regmap[TARGET_MAX] = {
> 28 [ANA] = vsc7514_ana_regmap,
> 29 [QS] = vsc7514_qs_regmap,
> 30 [QSYS] = vsc7514_qsys_regmap,
> 31 [REW] = vsc7514_rew_regmap,
> 32 [SYS] = vsc7514_sys_regmap,
> 33 [S0] = vsc7514_vcap_regmap,
34 [S1] = vsc7514_vcap_regmap,
35 [S2] = vsc7514_vcap_regmap,
> 36 [PTP] = vsc7514_ptp_regmap,
> 37 [DEV_GMII] = vsc7514_dev_gmii_regmap,
38 };
39
---
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: 40819 bytes --]
next prev parent reply other threads:[~2021-11-20 3:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 22:43 [PATCH v1 net-next 0/6] prepare ocelot for external interface control Colin Foster
2021-11-19 22:43 ` [PATCH v1 net-next 1/6] net: dsa: ocelot: remove unnecessary pci_bar variables Colin Foster
2021-11-19 22:43 ` [PATCH v1 net-next 2/6] net: dsa: ocelot: felix: Remove requirement for PCS in felix devices Colin Foster
2021-11-19 22:43 ` [PATCH v1 net-next 3/6] net: dsa: ocelot: felix: add interface for custom regmaps Colin Foster
2021-11-21 17:19 ` Vladimir Oltean
2021-11-22 16:45 ` Colin Foster
2021-12-04 0:11 ` Colin Foster
2021-12-04 12:07 ` Vladimir Oltean
2021-11-19 22:43 ` [PATCH v1 net-next 4/6] net: dsa: ocelot: felix: add per-device-per-port quirks Colin Foster
2021-11-21 17:13 ` Vladimir Oltean
2021-11-22 16:20 ` Colin Foster
2021-11-19 22:43 ` [PATCH v1 net-next 5/6] net: mscc: ocelot: split register definitions to a separate file Colin Foster
2021-11-20 1:16 ` kernel test robot
2021-11-20 3:23 ` kernel test robot [this message]
2021-11-21 17:09 ` Vladimir Oltean
2021-11-22 16:14 ` Colin Foster
2021-11-19 22:43 ` [PATCH v1 net-next 6/6] net: mscc: ocelot: expose ocelot wm functions Colin Foster
2021-11-21 17:07 ` Vladimir Oltean
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=202111201126.brIbRWKN-lkp@intel.com \
--to=lkp@intel.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=colin.foster@in-advantage.com \
--cc=f.fainelli@gmail.com \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
/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).