From: kernel test robot <lkp@intel.com>
To: Wei Fang <wei.fang@nxp.com>,
claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, yangbo.lu@nxp.com,
richardcochran@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Frank.Li@nxp.com
Cc: oe-kbuild-all@lists.linux.dev, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: enetc: use generic interfaces to get phc_index for ENETC v1
Date: Fri, 19 Sep 2025 10:14:44 +0800 [thread overview]
Message-ID: <202509191049.t301ozfh-lkp@intel.com> (raw)
In-Reply-To: <20250918074454.1742328-1-wei.fang@nxp.com>
Hi Wei,
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/Wei-Fang/net-enetc-use-generic-interfaces-to-get-phc_index-for-ENETC-v1/20250918-160739
base: net-next/main
patch link: https://lore.kernel.org/r/20250918074454.1742328-1-wei.fang%40nxp.com
patch subject: [PATCH net-next] net: enetc: use generic interfaces to get phc_index for ENETC v1
config: parisc-randconfig-001-20250919 (https://download.01.org/0day-ci/archive/20250919/202509191049.t301ozfh-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250919/202509191049.t301ozfh-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/202509191049.t301ozfh-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/freescale/enetc/enetc_ethtool.c: In function 'enetc_get_ts_info':
>> drivers/net/ethernet/freescale/enetc/enetc_ethtool.c:955:14: warning: unused variable 'phc_idx' [-Wunused-variable]
955 | int *phc_idx;
| ^~~~~~~
vim +/phc_idx +955 drivers/net/ethernet/freescale/enetc/enetc_ethtool.c
f5b9a1cde0a26c Wei Fang 2025-08-29 949
f5b9a1cde0a26c Wei Fang 2025-08-29 950 static int enetc_get_ts_info(struct net_device *ndev,
f5b9a1cde0a26c Wei Fang 2025-08-29 951 struct kernel_ethtool_ts_info *info)
f5b9a1cde0a26c Wei Fang 2025-08-29 952 {
f5b9a1cde0a26c Wei Fang 2025-08-29 953 struct enetc_ndev_priv *priv = netdev_priv(ndev);
f5b9a1cde0a26c Wei Fang 2025-08-29 954 struct enetc_si *si = priv->si;
f5b9a1cde0a26c Wei Fang 2025-08-29 @955 int *phc_idx;
f5b9a1cde0a26c Wei Fang 2025-08-29 956
f5b9a1cde0a26c Wei Fang 2025-08-29 957 if (!enetc_ptp_clock_is_enabled(si))
f5b9a1cde0a26c Wei Fang 2025-08-29 958 goto timestamp_tx_sw;
f5b9a1cde0a26c Wei Fang 2025-08-29 959
5f3b8f93ed1b53 Wei Fang 2025-09-18 960 info->phc_index = enetc_get_phc_index(si);
f5b9a1cde0a26c Wei Fang 2025-08-29 961 if (info->phc_index < 0)
f5b9a1cde0a26c Wei Fang 2025-08-29 962 goto timestamp_tx_sw;
f5b9a1cde0a26c Wei Fang 2025-08-29 963
f5b9a1cde0a26c Wei Fang 2025-08-29 964 enetc_get_ts_generic_info(ndev, info);
f5b9a1cde0a26c Wei Fang 2025-08-29 965
f5b9a1cde0a26c Wei Fang 2025-08-29 966 return 0;
f5b9a1cde0a26c Wei Fang 2025-08-29 967
f5b9a1cde0a26c Wei Fang 2025-08-29 968 timestamp_tx_sw:
f5b9a1cde0a26c Wei Fang 2025-08-29 969 info->so_timestamping = SOF_TIMESTAMPING_TX_SOFTWARE;
9c699a8f3b273c Martyn Welch 2024-09-12 970
41514737ecaa60 Y.b. Lu 2019-05-23 971 return 0;
41514737ecaa60 Y.b. Lu 2019-05-23 972 }
41514737ecaa60 Y.b. Lu 2019-05-23 973
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-09-19 2:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 7:44 [PATCH net-next] net: enetc: use generic interfaces to get phc_index for ENETC v1 Wei Fang
2025-09-18 12:48 ` Vladimir Oltean
2025-09-19 2:02 ` Wei Fang
2025-09-19 8:32 ` Kory Maincent
2025-09-19 8:48 ` Wei Fang
2025-09-22 23:33 ` Kory Maincent
2025-09-19 2:14 ` 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=202509191049.t301ozfh-lkp@intel.com \
--to=lkp@intel.com \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.com \
--cc=yangbo.lu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox