From: kernel test robot <lkp@intel.com>
To: Revanth Kumar Uppala <ruppala@nvidia.com>,
linux@armlinux.org.uk, andrew@lunn.ch, hkallweit1@gmail.com,
netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-tegra@vger.kernel.org,
Revanth Kumar Uppala <ruppala@nvidia.com>,
Narayan Reddy <narayanr@nvidia.com>
Subject: Re: [PATCH 4/4] net: phy: aqr113c: Enable Wake-on-LAN (WOL)
Date: Thu, 29 Jun 2023 02:57:23 +0800 [thread overview]
Message-ID: <202306290253.b8D3gQf8-lkp@intel.com> (raw)
In-Reply-To: <20230628124326.55732-4-ruppala@nvidia.com>
Hi Revanth,
kernel test robot noticed the following build warnings:
[auto build test WARNING on net/main]
[also build test WARNING on net-next/main linus/master horms-ipvs/master v6.4 next-20230628]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Revanth-Kumar-Uppala/net-phy-aquantia-Enable-MAC-Controlled-EEE/20230628-204746
base: net/main
patch link: https://lore.kernel.org/r/20230628124326.55732-4-ruppala%40nvidia.com
patch subject: [PATCH 4/4] net: phy: aqr113c: Enable Wake-on-LAN (WOL)
config: i386-randconfig-i013-20230628 (https://download.01.org/0day-ci/archive/20230629/202306290253.b8D3gQf8-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce: (https://download.01.org/0day-ci/archive/20230629/202306290253.b8D3gQf8-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/202306290253.b8D3gQf8-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/phy/aquantia_main.c: In function 'aqr_handle_interrupt':
>> drivers/net/phy/aquantia_main.c:476:29: warning: unused variable 'priv' [-Wunused-variable]
476 | struct aqr107_priv *priv = phydev->priv;
| ^~~~
vim +/priv +476 drivers/net/phy/aquantia_main.c
473
474 static irqreturn_t aqr_handle_interrupt(struct phy_device *phydev)
475 {
> 476 struct aqr107_priv *priv = phydev->priv;
477 int irq_status;
478 int ret;
479
480 ret = phy_read_mmd(phydev, MDIO_MMD_C22EXT, MDIO_C22EXT_GBE_PHY_SGMII_TX_ALARM1);
481 if (ret < 0) {
482 phy_error(phydev);
483 return IRQ_NONE;
484 }
485
486 if ((ret & MDIO_C22EXT_SGMII0_MAGIC_PKT_FRAME_MASK) ==
487 MDIO_C22EXT_SGMII0_MAGIC_PKT_FRAME_MASK) {
488 /* Disable the WoL */
489 ret = aqr113c_wol_disable(phydev);
490 if (ret < 0)
491 return IRQ_NONE;
492 }
493
494 irq_status = phy_read_mmd(phydev, MDIO_MMD_AN,
495 MDIO_AN_TX_VEND_INT_STATUS2);
496 if (irq_status < 0) {
497 phy_error(phydev);
498 return IRQ_NONE;
499 }
500
501 if (!(irq_status & MDIO_AN_TX_VEND_INT_STATUS2_MASK))
502 return IRQ_NONE;
503
504 phy_trigger_machine(phydev);
505
506 return IRQ_HANDLED;
507 }
508
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2023-06-28 18:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230628124326.55732-4-ruppala@nvidia.com>]
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=202306290253.b8D3gQf8-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=narayanr@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ruppala@nvidia.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 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).