From: kernel test robot <lkp@intel.com>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jakub Kicinski <kuba@kernel.org>
Subject: drivers/net/ethernet/marvell/octeontx2/af/cn20k/debugfs.c:25:32: error: 'struct rvu' has no member named 'rvu_dbg'; did you mean 'rvu_dl'?
Date: Fri, 26 Jun 2026 22:01:31 +0800 [thread overview]
Message-ID: <202606262158.Dvc57sU5-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4edcdefd4083ae04b1a5656f4be6cd83ae919ef4
commit: 1396771b0b7741d517d591cfb63333d3f97a8f6d octeontx2-af: npc: cn20k: Index management
date: 4 months ago
config: s390-randconfig-r134-20260626 (https://download.01.org/0day-ci/archive/20260626/202606262158.Dvc57sU5-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260626/202606262158.Dvc57sU5-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
| Fixes: 1396771b0b77 ("octeontx2-af: npc: cn20k: Index management")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606262158.Dvc57sU5-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/net/ethernet/marvell/octeontx2/af/cn20k/debugfs.c: In function 'npc_cn20k_debugfs_deinit':
>> drivers/net/ethernet/marvell/octeontx2/af/cn20k/debugfs.c:25:32: error: 'struct rvu' has no member named 'rvu_dbg'; did you mean 'rvu_dl'?
debugfs_remove_recursive(rvu->rvu_dbg.npc);
^~~~~~~
rvu_dl
vim +25 drivers/net/ethernet/marvell/octeontx2/af/cn20k/debugfs.c
22
23 void npc_cn20k_debugfs_deinit(struct rvu *rvu)
24 {
> 25 debugfs_remove_recursive(rvu->rvu_dbg.npc);
26 }
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-06-26 14:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202606262158.Dvc57sU5-lkp@intel.com \
--to=lkp@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rkannoth@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.