From: kernel test robot <lkp@intel.com>
To: Raju Rangoju <Raju.Rangoju@amd.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, pabeni@redhat.com,
kuba@kernel.org, edumazet@google.com, davem@davemloft.net,
andrew+netdev@lunn.ch, Shyam-sundar.S-k@amd.com,
Raju Rangoju <Raju.Rangoju@amd.com>
Subject: Re: [PATCH net-next v2 2/4] amd-xgbe: add ethtool phy selftest
Date: Sat, 18 Oct 2025 11:33:20 +0800 [thread overview]
Message-ID: <202510181124.5LDfdemg-lkp@intel.com> (raw)
In-Reply-To: <20251017064704.3911798-3-Raju.Rangoju@amd.com>
Hi Raju,
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/Raju-Rangoju/amd-xgbe-introduce-support-ethtool-selftest/20251017-151230
base: net-next/main
patch link: https://lore.kernel.org/r/20251017064704.3911798-3-Raju.Rangoju%40amd.com
patch subject: [PATCH net-next v2 2/4] amd-xgbe: add ethtool phy selftest
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20251018/202510181124.5LDfdemg-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251018/202510181124.5LDfdemg-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/202510181124.5LDfdemg-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/amd/xgbe/xgbe-selftest.c: In function 'xgbe_selftest_get_strings':
>> drivers/net/ethernet/amd/xgbe/xgbe-selftest.c:427:52: warning: '%s' directive output may be truncated writing up to 95 bytes into a region of size 28 [-Wformat-truncation=]
427 | snprintf(p, ETH_GSTRING_LEN, "%2d. %s", i + 1,
| ^~
drivers/net/ethernet/amd/xgbe/xgbe-selftest.c:427:17: note: 'snprintf' output between 5 and 100 bytes into a destination of size 32
427 | snprintf(p, ETH_GSTRING_LEN, "%2d. %s", i + 1,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
428 | xgbe_selftests[i].name);
| ~~~~~~~~~~~~~~~~~~~~~~~
vim +427 drivers/net/ethernet/amd/xgbe/xgbe-selftest.c
066e40696db52b Raju Rangoju 2025-10-17 420
066e40696db52b Raju Rangoju 2025-10-17 421 void xgbe_selftest_get_strings(struct xgbe_prv_data *pdata, u8 *data)
066e40696db52b Raju Rangoju 2025-10-17 422 {
066e40696db52b Raju Rangoju 2025-10-17 423 u8 *p = data;
066e40696db52b Raju Rangoju 2025-10-17 424 int i;
066e40696db52b Raju Rangoju 2025-10-17 425
066e40696db52b Raju Rangoju 2025-10-17 426 for (i = 0; i < xgbe_selftest_get_count(pdata); i++) {
066e40696db52b Raju Rangoju 2025-10-17 @427 snprintf(p, ETH_GSTRING_LEN, "%2d. %s", i + 1,
066e40696db52b Raju Rangoju 2025-10-17 428 xgbe_selftests[i].name);
066e40696db52b Raju Rangoju 2025-10-17 429 p += ETH_GSTRING_LEN;
066e40696db52b Raju Rangoju 2025-10-17 430 }
066e40696db52b Raju Rangoju 2025-10-17 431 }
066e40696db52b Raju Rangoju 2025-10-17 432
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-10-18 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 6:47 [PATCH net-next v2 0/4] amd-xgbe: introduce support for ethtool selftests Raju Rangoju
2025-10-17 6:47 ` [PATCH net-next v2 1/4] amd-xgbe: introduce support ethtool selftest Raju Rangoju
2025-10-19 5:42 ` kernel test robot
2025-10-17 6:47 ` [PATCH net-next v2 2/4] amd-xgbe: add ethtool phy selftest Raju Rangoju
2025-10-18 3:33 ` kernel test robot [this message]
2025-10-17 6:47 ` [PATCH net-next v2 3/4] amd-xgbe: add ethtool split header selftest Raju Rangoju
2025-10-17 6:47 ` [PATCH net-next v2 4/4] amd-xgbe: add ethtool jumbo frame selftest Raju Rangoju
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=202510181124.5LDfdemg-lkp@intel.com \
--to=lkp@intel.com \
--cc=Raju.Rangoju@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.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).