From: kernel test robot <lkp@intel.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Simon Horman <horms@kernel.org>
Subject: drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c:3938:28: error: no member named 'ixgbe_dbg_adapter' in 'struct ixgbe_adapter'
Date: Sat, 1 Nov 2025 15:35:47 +0800 [thread overview]
Message-ID: <202511011546.mIG3y3Pt-lkp@intel.com> (raw)
Hi Michal,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ba36dd5ee6fd4643ebbf6ee6eefcecf0b07e35c7
commit: 641585bc978e0a1170ca8f12fbb1468b3874a2db ixgbe: fwlog support for e610
date: 7 weeks ago
config: powerpc-skiroot_defconfig (https://download.01.org/0day-ci/archive/20251101/202511011546.mIG3y3Pt-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project cc271437553452ede002d871d32abc02084341a8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251101/202511011546.mIG3y3Pt-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/202511011546.mIG3y3Pt-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c:3938:28: error: no member named 'ixgbe_dbg_adapter' in 'struct ixgbe_adapter'
3938 | .debugfs_root = adapter->ixgbe_dbg_adapter,
| ~~~~~~~ ^
1 error generated.
vim +3938 drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c
3931
3932 int ixgbe_fwlog_init(struct ixgbe_hw *hw)
3933 {
3934 struct ixgbe_adapter *adapter = hw->back;
3935 struct libie_fwlog_api api = {
3936 .pdev = adapter->pdev,
3937 .send_cmd = __fwlog_send_cmd,
> 3938 .debugfs_root = adapter->ixgbe_dbg_adapter,
3939 .priv = hw,
3940 };
3941
3942 if (hw->mac.type != ixgbe_mac_e610)
3943 return -EOPNOTSUPP;
3944
3945 return libie_fwlog_init(&hw->fwlog, &api);
3946 }
3947
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-01 7:36 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=202511011546.mIG3y3Pt-lkp@intel.com \
--to=lkp@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=michal.swiatkowski@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=przemyslaw.kitszel@intel.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
all inboxes | Powered by JetHome®