From: kernel test robot <lkp@intel.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>, davem@davemloft.net
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Maxime Chevallier" <maxime.chevallier@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, thomas.petazzoni@bootlin.com,
"Andrew Lunn" <andrew@lunn.ch>,
"Jakub Kicinski" <kuba@kernel.org>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"Herve Codina" <herve.codina@bootlin.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Heiner Kallweit" <hkallweit1@gmail.com>,
"Vladimir Oltean" <vladimir.oltean@nxp.com>,
"Köry Maincent" <kory.maincent@bootlin.com>,
"Marek Behún" <kabel@kernel.org>,
"Oleksij Rempel" <o.rempel@pengutronix.de>,
"Nicolò Veronese" <nicveronese@gmail.com>,
"Simon Horman" <horms@kernel.org>,
mwojtas@chromium.org, "Antoine Tenart" <atenart@kernel.org>,
devicetree@vger.kernel.org, "Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Romain Gantois" <romain.gantois@bootlin.com>,
"Daniel Golle" <daniel@makrotopia.org>
Subject: Re: [PATCH net-next v11 08/16] net: phy: Introduce generic SFP handling for PHY drivers
Date: Fri, 15 Aug 2025 11:25:55 +0800 [thread overview]
Message-ID: <202508151058.jqJsn9VB-lkp@intel.com> (raw)
In-Reply-To: <20250814135832.174911-9-maxime.chevallier@bootlin.com>
Hi Maxime,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Maxime-Chevallier/dt-bindings-net-Introduce-the-ethernet-connector-description/20250814-221559
base: net-next/main
patch link: https://lore.kernel.org/r/20250814135832.174911-9-maxime.chevallier%40bootlin.com
patch subject: [PATCH net-next v11 08/16] net: phy: Introduce generic SFP handling for PHY drivers
config: i386-randconfig-013-20250815 (https://download.01.org/0day-ci/archive/20250815/202508151058.jqJsn9VB-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250815/202508151058.jqJsn9VB-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/202508151058.jqJsn9VB-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/phy/phy_device.c:1625:47: warning: variable 'iface' is uninitialized when used here [-Wuninitialized]
1625 | return port->ops->configure_mii(port, true, iface);
| ^~~~~
drivers/net/phy/phy_device.c:1597:2: note: variable 'iface' is declared here
1597 | phy_interface_t iface;
| ^
1 warning generated.
vim +/iface +1625 drivers/net/phy/phy_device.c
1589
1590 static int phy_sfp_module_insert(void *upstream, const struct sfp_eeprom_id *id)
1591 {
1592 struct phy_device *phydev = upstream;
1593 struct phy_port *port;
1594
1595 __ETHTOOL_DECLARE_LINK_MODE_MASK(sfp_support);
1596 DECLARE_PHY_INTERFACE_MASK(interfaces);
1597 phy_interface_t iface;
1598
1599 linkmode_zero(sfp_support);
1600
1601 port = phy_get_sfp_port(phydev);
1602 if (!port)
1603 return -EINVAL;
1604
1605 sfp_parse_support(phydev->sfp_bus, id, sfp_support, interfaces);
1606
1607 if (phydev->n_ports == 1)
1608 phydev->port = sfp_parse_port(phydev->sfp_bus, id, sfp_support);
1609
1610 linkmode_and(sfp_support, port->supported, sfp_support);
1611 linkmode_and(interfaces, interfaces, port->interfaces);
1612
1613 if (linkmode_empty(sfp_support)) {
1614 dev_err(&phydev->mdio.dev, "incompatible SFP module inserted, no common linkmode\n");
1615 return -EINVAL;
1616 }
1617
1618 /* Check that this interface is supported */
1619 if (!test_bit(iface, port->interfaces)) {
1620 dev_err(&phydev->mdio.dev, "PHY %s does not support the SFP module's requested MII interfaces\n", phydev_name(phydev));
1621 return -EINVAL;
1622 }
1623
1624 if (port->ops && port->ops->configure_mii)
> 1625 return port->ops->configure_mii(port, true, iface);
1626
1627 return 0;
1628 }
1629
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-15 3:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:58 [PATCH net-next v11 00/16] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 01/16] dt-bindings: net: Introduce the ethernet-connector description Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 02/16] net: ethtool: common: Indicate that BaseT works on up to 4 lanes Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 03/16] net: ethtool: Introduce ETHTOOL_LINK_MEDIUM_* values Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 04/16] net: phy: Introduce PHY ports representation Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 05/16] net: phy: dp83822: Add support for phy_port representation Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 06/16] dt-bindings: net: dp83822: Deprecate ti,fiber-mode Maxime Chevallier
2025-08-14 22:34 ` Rob Herring
2025-08-14 13:58 ` [PATCH net-next v11 07/16] net: phy: Create a phy_port for PHY-driven SFPs Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 08/16] net: phy: Introduce generic SFP handling for PHY drivers Maxime Chevallier
2025-08-15 3:25 ` kernel test robot [this message]
2025-08-22 9:59 ` Maxime Chevallier
2025-08-27 14:10 ` Simon Horman
2025-08-14 13:58 ` [PATCH net-next v11 09/16] net: phy: marvell-88x2222: Support SFP through phy_port interface Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 10/16] net: phy: marvell: " Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 11/16] net: phy: marvell10g: Support SFP through phy_port Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 12/16] net: phy: at803x: Support SFP through phy_port interface Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 13/16] net: phy: qca807x: " Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 14/16] net: phy: Only rely on phy_port for PHY-driven SFP Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 15/16] net: phy: dp83822: Add SFP support through the phy_port interface Maxime Chevallier
2025-08-14 13:58 ` [PATCH net-next v11 16/16] Documentation: networking: Document the phy_port infrastructure Maxime Chevallier
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=202508151058.jqJsn9VB-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=herve.codina@bootlin.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kabel@kernel.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=llvm@lists.linux.dev \
--cc=maxime.chevallier@bootlin.com \
--cc=mwojtas@chromium.org \
--cc=netdev@vger.kernel.org \
--cc=nicveronese@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=romain.gantois@bootlin.com \
--cc=thomas.petazzoni@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.