From: kernel test robot <lkp@intel.com>
To: Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: oe-kbuild-all@lists.linux.dev, anthony.l.nguyen@intel.com,
netdev@vger.kernel.org,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2] ixgbe: E610: force phy link to get down when interface is down
Date: Tue, 7 Jul 2026 00:09:43 +0800 [thread overview]
Message-ID: <202607070035.qAAqVjGH-lkp@intel.com> (raw)
In-Reply-To: <20260706094330.186341-1-jedrzej.jagielski@intel.com>
Hi Jedrzej,
kernel test robot noticed the following build errors:
[auto build test ERROR on tnguy-next-queue/dev-queue]
url: https://github.com/intel-lab-lkp/linux/commits/Jedrzej-Jagielski/ixgbe-E610-force-phy-link-to-get-down-when-interface-is-down/20260706-180351
base: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
patch link: https://lore.kernel.org/r/20260706094330.186341-1-jedrzej.jagielski%40intel.com
patch subject: [Intel-wired-lan] [PATCH iwl-next v2] ixgbe: E610: force phy link to get down when interface is down
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20260707/202607070035.qAAqVjGH-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260707/202607070035.qAAqVjGH-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/202607070035.qAAqVjGH-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c: In function 'ixgbe_close':
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:7572:25: error: implicit declaration of function 'e_error'; did you mean 'e_err'? [-Wimplicit-function-declaration]
7572 | e_error(drv, "Cannot set PHY link down\n");
| ^~~~~~~
| e_err
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:7572:33: error: 'drv' undeclared (first use in this function)
7572 | e_error(drv, "Cannot set PHY link down\n");
| ^~~
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:7572:33: note: each undeclared identifier is reported only once for each function it appears in
vim +7572 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
7544
7545 /**
7546 * ixgbe_close - Disables a network interface
7547 * @netdev: network interface device structure
7548 *
7549 * Returns 0, this is not allowed to fail
7550 *
7551 * The close entry point is called when an interface is de-activated
7552 * by the OS. The hardware is still under the drivers control, but
7553 * needs to be disabled. A global MAC reset is issued to stop the
7554 * hardware, and all transmit and receive resources are freed.
7555 **/
7556 int ixgbe_close(struct net_device *netdev)
7557 {
7558 struct ixgbe_adapter *adapter = ixgbe_from_netdev(netdev);
7559
7560 ixgbe_ptp_stop(adapter);
7561
7562 if (netif_device_present(netdev))
7563 ixgbe_close_suspend(adapter);
7564
7565 ixgbe_fdir_filter_exit(adapter);
7566
7567 if (adapter->flags2 & IXGBE_FLAG2_LINK_DOWN_ON_CLOSE) {
7568 int err;
7569
7570 err = ixgbe_disable_phy_link(&adapter->hw);
7571 if (err)
> 7572 e_error(drv, "Cannot set PHY link down\n");
7573
7574 ixgbe_handle_link_down(adapter);
7575 }
7576
7577 ixgbe_release_hw_control(adapter);
7578
7579 return 0;
7580 }
7581
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-07-06 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 9:43 [PATCH iwl-next v2] ixgbe: E610: force phy link to get down when interface is down Jedrzej Jagielski
2026-07-06 15:27 ` [Intel-wired-lan] " kernel test robot
2026-07-06 16:09 ` kernel 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=202607070035.qAAqVjGH-lkp@intel.com \
--to=lkp@intel.com \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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