From: kernel test robot <lkp@intel.com>
To: Potnuri Bharat Teja <bharat@chelsio.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, davem@davemloft.net,
kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, bharat@chelsio.com
Subject: Re: [PATCH net-next v4 11/12] cxgb4: extend debugfs support for T7 adapters
Date: Thu, 15 Oct 2026 22:08:33 +0800 [thread overview]
Message-ID: <202610152202.xxgjlBCN-lkp@intel.com> (raw)
In-Reply-To: <20261014221257.436789-12-bharat@chelsio.com>
Hi Potnuri,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.3-rc7 next-20261012]
[cannot apply to horms-ipvs/master]
[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/Potnuri-Bharat-Teja/cxgb4-add-T7-hardware-definitions-and-firmware-interfaces/20261014-181246
base: linus/master
patch link: https://lore.kernel.org/r/20261014221257.436789-12-bharat%40chelsio.com
patch subject: [PATCH net-next v4 11/12] cxgb4: extend debugfs support for T7 adapters
config: x86_64-randconfig-1000-20261015 (https://download.01.org/0day-ci/archive/20261015/202610152202.xxgjlBCN-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610152202.xxgjlBCN-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/202610152202.xxgjlBCN-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c: In function 'cxgb4_setup_debugfs':
>> drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c:4365:32: error: 'clip_tbl_fops' undeclared (first use in this function); did you mean 'cctrl_tbl_fops'?
4365 | { "clip_tbl", &clip_tbl_fops, 0400, 0 },
| ^~~~~~~~~~~~~
| cctrl_tbl_fops
drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c:4365:32: note: each undeclared identifier is reported only once for each function it appears in
vim +4365 drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c
4355
4356 int cxgb4_setup_debugfs(struct adapter *adap)
4357 {
4358 static struct t4_linux_debugfs_entry cxgb4_debugfs_files[] = {
4359 { "blocked_fl", &blocked_fl_fops, 0600 },
4360 #ifdef CONFIG_CHELSIO_T4_DCB
4361 { "dcb_info", &dcb_info_debugfs_fops, 0400, 0 },
4362 #endif /* CONFIG_CHELSIO_T4_DCB */
4363 { "resources", &resources_fops, 0400, 0 },
4364 { "sge_qinfo", &sge_qinfo_debugfs_fops, 0400, 0 },
> 4365 { "clip_tbl", &clip_tbl_fops, 0400, 0 },
4366 { "tids", &tid_info_fops, 0400, 0 },
4367 { "trace0", &mps_trc_debugfs_fops, 0600, 0 },
4368 { "trace1", &mps_trc_debugfs_fops, 0600, 1 },
4369 { "trace2", &mps_trc_debugfs_fops, 0600, 2 },
4370 { "trace3", &mps_trc_debugfs_fops, 0600, 3 },
4371 { "l2t", &t4_l2t_fops, 0400, 0 },
4372 { "crypto", &chcr_stats_fops, 0400, 0 },
4373 };
4374
4375 static struct t4_linux_debugfs_entry cxgb4_t7_debugfs_files[] = {
4376 { "trace4", &mps_trc_debugfs_fops, 0600, 4 },
4377 { "trace5", &mps_trc_debugfs_fops, 0600, 5 },
4378 { "trace6", &mps_trc_debugfs_fops, 0600, 6 },
4379 { "trace7", &mps_trc_debugfs_fops, 0600, 7 },
4380 };
4381
4382 if (IS_ERR_OR_NULL(adap->debugfs_root))
4383 return -1;
4384
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-15 14:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 22:12 [PATCH net-next v4 00/12] cxgb4: Add T7 adapter support Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 01/12] cxgb4: add T7 hardware definitions and firmware interfaces Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 02/12] cxgb4: rework the interrupt handling framework Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 03/12] cxgb4: add T7 hardware management support Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 04/12] cxgb4: move PCI device management into cxgb4_pci.c and rework driver helpers Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 05/12] cxgb4: add T7 support to the main driver Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 06/12] cxgb4: update PTP register access for T7 Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 07/12] cxgb4: extend ethtool support for T7 adapters Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 08/12] cxgb4: Add T7 support to the filter infrastructure Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 09/12] cxgb4: Add indirect register definitions for T7 Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 10/12] cxgb4: extend CUDBG support for T7 adapters Potnuri Bharat Teja
2026-10-14 22:12 ` [PATCH net-next v4 11/12] cxgb4: extend debugfs " Potnuri Bharat Teja
2026-10-15 14:08 ` kernel test robot [this message]
2026-10-14 22:12 ` [PATCH net-next v4 12/12] cxgb4: select ULD Tx and control queues by TID on T7 Potnuri Bharat Teja
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=202610152202.xxgjlBCN-lkp@intel.com \
--to=lkp@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=bharat@chelsio.com \
--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