From: kernel test robot <lkp@intel.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>
Cc: oe-kbuild-all@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
Jakub Kicinski <kuba@kernel.org>
Subject: [arm:zii 40/102] drivers/net/dsa/b53/b53_common.c:1484:34: error: initialization of 'struct ethtool_keee *' from incompatible pointer type 'struct ethtool_eee *'
Date: Fri, 10 May 2024 01:13:09 +0800 [thread overview]
Message-ID: <202405100102.n1YFCS8g-lkp@intel.com> (raw)
tree: git://git.armlinux.org.uk/~rmk/linux-arm.git zii
head: e9436a5c3f1e8dc9d425f51b98e96e185a20704d
commit: 7e189be0111c723d361907eecee7f5f96000b518 [40/102] net: dsa: b53: Call b53_eee_init() from b53_mac_link_up()
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240510/202405100102.n1YFCS8g-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240510/202405100102.n1YFCS8g-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405100102.n1YFCS8g-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/dsa/b53/b53_common.c: In function 'b53_phylink_mac_link_up':
>> drivers/net/dsa/b53/b53_common.c:1484:34: error: initialization of 'struct ethtool_keee *' from incompatible pointer type 'struct ethtool_eee *' [-Werror=incompatible-pointer-types]
1484 | struct ethtool_keee *p = &dev->ports[port].eee;
| ^
>> drivers/net/dsa/b53/b53_common.c:1488:18: error: invalid use of undefined type 'struct ethtool_keee'
1488 | p->eee_enabled = b53_eee_init(ds, port, phydev);
| ^~
cc1: some warnings being treated as errors
vim +1484 drivers/net/dsa/b53/b53_common.c
1475
1476 static void b53_phylink_mac_link_up(struct dsa_switch *ds, int port,
1477 unsigned int mode,
1478 phy_interface_t interface,
1479 struct phy_device *phydev,
1480 int speed, int duplex,
1481 bool tx_pause, bool rx_pause)
1482 {
1483 struct b53_device *dev = ds->priv;
> 1484 struct ethtool_keee *p = &dev->ports[port].eee;
1485
1486 if (mode == MLO_AN_PHY) {
1487 /* Re-negotiate EEE if it was enabled already */
> 1488 p->eee_enabled = b53_eee_init(ds, port, phydev);
1489 return;
1490 }
1491
1492 if (mode == MLO_AN_FIXED) {
1493 /* Force flow control on BCM5301x's CPU port */
1494 if (is5301x(dev) && dsa_is_cpu_port(ds, port))
1495 tx_pause = rx_pause = true;
1496
1497 b53_force_port_config(dev, port, speed, duplex,
1498 tx_pause, rx_pause);
1499 b53_force_link(dev, port, true);
1500 return;
1501 }
1502
1503 if (phy_interface_mode_is_8023z(interface) &&
1504 dev->ops->serdes_link_set)
1505 dev->ops->serdes_link_set(dev, port, mode, interface, true);
1506 }
1507
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
reply other threads:[~2024-05-09 17:13 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=202405100102.n1YFCS8g-lkp@intel.com \
--to=lkp@intel.com \
--cc=florian.fainelli@broadcom.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).