From: kernel test robot <lkp@intel.com>
To: Rory Little <rory@candelatech.com>,
nbd@nbd.name, lorenzo@kernel.org, ryder.lee@mediatek.com
Cc: oe-kbuild-all@lists.linux.dev, shayne.chen@mediatek.com,
sean.wang@mediatek.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH mt76 v2 1/4] wifi: mt76: mt7996: Add per-radio phy debugfs directories.
Date: Wed, 7 May 2025 14:06:06 +0800 [thread overview]
Message-ID: <202505071352.R4Bb2GN1-lkp@intel.com> (raw)
In-Reply-To: <20250430232225.3943242-2-rory@candelatech.com>
Hi Rory,
kernel test robot noticed the following build warnings:
[auto build test WARNING on wireless-next/main]
[also build test WARNING on wireless/main linus/master v6.15-rc5 next-20250506]
[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/Rory-Little/wifi-mt76-mt7996-Add-per-radio-phy-debugfs-directories/20250501-072345
base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link: https://lore.kernel.org/r/20250430232225.3943242-2-rory%40candelatech.com
patch subject: [PATCH mt76 v2 1/4] wifi: mt76: mt7996: Add per-radio phy debugfs directories.
config: openrisc-allyesconfig (https://download.01.org/0day-ci/archive/20250507/202505071352.R4Bb2GN1-lkp@intel.com/config)
compiler: or1k-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250507/202505071352.R4Bb2GN1-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/202505071352.R4Bb2GN1-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/wireless/mediatek/mt76/mt7996/debugfs.c: In function 'mt7996_init_debugfs':
>> drivers/net/wireless/mediatek/mt76/mt7996/debugfs.c:851:52: warning: 'snprintf' output may be truncated before the last format character [-Wformat-truncation=]
851 | snprintf(fname, sizeof(fname), "radio_phy%d", phy->mt76->band_idx);
| ^
In function 'mt7996_init_radio_phy_debugfs',
inlined from 'mt7996_init_debugfs' at drivers/net/wireless/mediatek/mt76/mt7996/debugfs.c:900:9:
drivers/net/wireless/mediatek/mt76/mt7996/debugfs.c:851:9: note: 'snprintf' output between 11 and 13 bytes into a destination of size 12
851 | snprintf(fname, sizeof(fname), "radio_phy%d", phy->mt76->band_idx);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/snprintf +851 drivers/net/wireless/mediatek/mt76/mt7996/debugfs.c
841
842 DEFINE_DEBUGFS_ATTRIBUTE(fops_rf_regval, mt7996_rf_regval_get,
843 mt7996_rf_regval_set, "0x%08llx\n");
844
845 static int
846 mt7996_init_radio_phy_debugfs(struct mt7996_phy *phy)
847 {
848 struct dentry *dir;
849 char fname[12];
850
> 851 snprintf(fname, sizeof(fname), "radio_phy%d", phy->mt76->band_idx);
852 dir = debugfs_create_dir(fname, phy->dev->debugfs_dir);
853
854 if (IS_ERR_OR_NULL(dir))
855 return -ENOMEM;
856
857 phy->debugfs_dir = dir;
858
859 return 0;
860 }
861
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-05-07 6:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 23:22 [PATCH mt76 v2 0/4] wifi: mt76: mt7996: rx filter fixes and improvements Rory Little
2025-04-30 23:22 ` [PATCH mt76 v2 1/4] wifi: mt76: mt7996: Add per-radio phy debugfs directories Rory Little
2025-05-07 6:06 ` kernel test robot [this message]
2025-05-07 20:57 ` Rory Little
2025-04-30 23:22 ` [PATCH mt76 v2 2/4] wifi: mt76: mt7996: Add debugfs file for rxfilter Rory Little
2025-04-30 23:22 ` [PATCH mt76 v2 3/4] wifi: mt76: mt7996: Refactor of rx filter logic Rory Little
2025-04-30 23:22 ` [PATCH mt76 v2 4/4] wifi: mt76: mt7996: Allow monitor enable if phy is already running Rory Little
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=202505071352.R4Bb2GN1-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rory@candelatech.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.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