From: kbuild test robot <lkp@intel.com>
To: Jack Ping CHNG <jack.ping.chng@intel.com>
Cc: kbuild-all@lists.01.org, devel@driverdev.osuosl.org,
cheol.yong.kim@intel.com,
Jack Ping CHNG <jack.ping.chng@intel.com>,
andriy.shevchenko@intel.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Amireddy Mallikarjuna reddy
<mallikarjunax.reddy@linux.intel.com>,
gregkh@linuxfoundation.org, davem@davemloft.net
Subject: Re: [PATCH v2] staging: intel-gwdpa: gswip: Introduce Gigabit Ethernet Switch (GSWIP) device driver
Date: Tue, 17 Dec 2019 00:16:18 +0800 [thread overview]
Message-ID: <201912162303.vLkPGaFz%lkp@intel.com> (raw)
In-Reply-To: <5f85180573a3fb20238d6a340cdd990f140ed6f0.1576054234.git.jack.ping.chng@intel.com>
[-- Attachment #1: Type: text/plain, Size: 3798 bytes --]
Hi Jack,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on staging/staging-testing]
[also build test ERROR on v5.5-rc1]
[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/Jack-Ping-CHNG/staging-intel-gwdpa-gswip-Introduce-Gigabit-Ethernet-Switch-GSWIP-device-driver/20191212-073318
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git 4d17363db021311d0b5ad533bc9c438ed3177d7c
config: s390-allmodconfig (attached as .config)
compiler: s390-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=s390
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All error/warnings (new ones prefixed by >>):
In file included from drivers/staging/intel-gwdpa/gswip/mac_cfg.c:5:0:
drivers/staging/intel-gwdpa/gswip/mac_common.h: In function 'sw_write':
>> drivers/staging/intel-gwdpa/gswip/mac_common.h:175:2: error: implicit declaration of function 'writel'; did you mean 'sw_write'? [-Werror=implicit-function-declaration]
writel(val, priv->sw + reg);
^~~~~~
sw_write
drivers/staging/intel-gwdpa/gswip/mac_common.h: In function 'sw_read':
>> drivers/staging/intel-gwdpa/gswip/mac_common.h:181:9: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
return readl(priv->sw + reg);
^~~~~
drivers/staging/intel-gwdpa/gswip/mac_cfg.c: In function 'mac_set_physpeed':
>> drivers/staging/intel-gwdpa/gswip/mac_cfg.c:55:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
sw_set_speed(priv, SPEED_10M);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/staging/intel-gwdpa/gswip/mac_cfg.c:57:2: note: here
case SPEED_XGMAC_100M:
^~~~
drivers/staging/intel-gwdpa/gswip/mac_cfg.c:67:3: warning: this statement may fall through [-Wimplicit-fallthrough=]
sw_set_speed(priv, SPEED_10M);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/staging/intel-gwdpa/gswip/mac_cfg.c:69:2: note: here
case SPEED_LMAC_100M:
^~~~
cc1: some warnings being treated as errors
--
In file included from drivers/staging/intel-gwdpa/gswip/gswip_mac.c:7:0:
drivers/staging/intel-gwdpa/gswip/mac_common.h: In function 'sw_write':
>> drivers/staging/intel-gwdpa/gswip/mac_common.h:175:2: error: implicit declaration of function 'writel'; did you mean 'sw_write'? [-Werror=implicit-function-declaration]
writel(val, priv->sw + reg);
^~~~~~
sw_write
drivers/staging/intel-gwdpa/gswip/mac_common.h: In function 'sw_read':
>> drivers/staging/intel-gwdpa/gswip/mac_common.h:181:9: error: implicit declaration of function 'readl' [-Werror=implicit-function-declaration]
return readl(priv->sw + reg);
^~~~~
cc1: some warnings being treated as errors
vim +175 drivers/staging/intel-gwdpa/gswip/mac_common.h
171
172 /* GSWIP-O Top Register write */
173 static inline void sw_write(struct gswip_mac *priv, u32 reg, u32 val)
174 {
> 175 writel(val, priv->sw + reg);
176 }
177
178 /* GSWIP-O Top Register read */
179 static inline int sw_read(struct gswip_mac *priv, u32 reg)
180 {
> 181 return readl(priv->sw + reg);
182 }
183
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 57234 bytes --]
prev parent reply other threads:[~2019-12-16 16:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 8:57 [PATCH v2] staging: intel-gwdpa: gswip: Introduce Gigabit Ethernet Switch (GSWIP) device driver Jack Ping CHNG
2019-12-11 9:27 ` Greg KH
[not found] ` <BYAPR11MB317606F8BE2B60C4BAD872F1DE5A0@BYAPR11MB3176.namprd11.prod.outlook.com>
[not found] ` <c26e56cf-eb04-5992-252a-e66f6029d6ac@linux.intel.com>
2019-12-11 12:17 ` FW: " Greg KH
2019-12-11 16:03 ` Andrew Lunn
2019-12-11 9:29 ` Greg KH
2019-12-11 10:57 ` Dan Carpenter
[not found] ` <BYAPR11MB3176EB0A2BF59AAF161D4174DE5A0@BYAPR11MB3176.namprd11.prod.outlook.com>
2019-12-12 7:25 ` Chng, Jack Ping
2019-12-16 16:16 ` kbuild 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=201912162303.vLkPGaFz%lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=cheol.yong.kim@intel.com \
--cc=davem@davemloft.net \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=jack.ping.chng@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunax.reddy@linux.intel.com \
--cc=netdev@vger.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).