From: kbuild test robot <lkp@intel.com>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: kbuild-all@lists.01.org, linux-arm-kernel@lists.infradead.org
Subject: [arm:zii 109/125] drivers/net/phy/marvell10g.c:332:2: error: too many arguments to function 'sfp_parse_support'
Date: Tue, 3 Mar 2020 23:41:53 +0800 [thread overview]
Message-ID: <202003032339.yZueFZO2%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
tree: git://git.armlinux.org.uk/~rmk/linux-arm.git zii
head: bca3ce80a604693842453e39f7cc4446c3603ed6
commit: a4eebbf05a74c7747ee75eacca04c0886ba2cc74 [109/125] net: sfp: add interface bitmap
config: arm64-defconfig (attached as .config)
compiler: aarch64-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
git checkout a4eebbf05a74c7747ee75eacca04c0886ba2cc74
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/net/phy/marvell10g.c: In function 'mv3310_sfp_insert':
>> drivers/net/phy/marvell10g.c:332:2: error: too many arguments to function 'sfp_parse_support'
sfp_parse_support(phydev->sfp_bus, id, support, interfaces);
^~~~~~~~~~~~~~~~~
In file included from drivers/net/phy/marvell10g.c:31:0:
include/linux/sfp.h:566:20: note: declared here
static inline void sfp_parse_support(struct sfp_bus *bus,
^~~~~~~~~~~~~~~~~
vim +/sfp_parse_support +332 drivers/net/phy/marvell10g.c
324
325 static int mv3310_sfp_insert(void *upstream, const struct sfp_eeprom_id *id)
326 {
327 struct phy_device *phydev = upstream;
328 __ETHTOOL_DECLARE_LINK_MODE_MASK(support) = { 0, };
329 DECLARE_PHY_INTERFACE_MASK(interfaces);
330 phy_interface_t iface;
331
> 332 sfp_parse_support(phydev->sfp_bus, id, support, interfaces);
333 iface = sfp_select_interface(phydev->sfp_bus, support);
334
335 if (iface != PHY_INTERFACE_MODE_10GBASER) {
336 dev_err(&phydev->mdio.dev, "incompatible SFP module inserted\n");
337 return -EINVAL;
338 }
339 return 0;
340 }
341
---
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: 46452 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
reply other threads:[~2020-03-03 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202003032339.yZueFZO2%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
/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).