From: kernel test robot <lkp@intel.com>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Intel Wired LAN <intel-wired-lan@lists.osuosl.org>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>
Subject: [Intel-wired-lan] [tnguy-next-queue:dev-queue 83/96] drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:3360: undefined reference to `libie_get_fwlog_data'
Date: Mon, 25 Aug 2025 18:13:08 +0800 [thread overview]
Message-ID: <202508251750.6y0aVhmt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
head: 477bd744709ed3884ba4544574e78706358b627a
commit: 8a3ba7f03f335554bbde8ae17798a21e4a3b62ad [83/96] ixgbe: fwlog support for e610
config: x86_64-randconfig-006-20250825 (https://download.01.org/0day-ci/archive/20250825/202508251750.6y0aVhmt-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250825/202508251750.6y0aVhmt-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/202508251750.6y0aVhmt-lkp@intel.com/
All errors (new ones prefixed by >>):
ld: vmlinux.o: in function `ixgbe_handle_fw_event':
>> drivers/net/ethernet/intel/ixgbe/ixgbe_main.c:3360: undefined reference to `libie_get_fwlog_data'
ld: vmlinux.o: in function `ixgbe_fwlog_init':
>> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c:3945: undefined reference to `libie_fwlog_init'
ld: vmlinux.o: in function `ixgbe_fwlog_deinit':
>> drivers/net/ethernet/intel/ixgbe/ixgbe_e610.c:3953: undefined reference to `libie_fwlog_deinit'
vim +3360 drivers/net/ethernet/intel/ixgbe/ixgbe_main.c
3324
3325 /**
3326 * ixgbe_handle_fw_event - handle Firmware event
3327 * @adapter: pointer to the adapter structure
3328 *
3329 * Obtain an event from the ACI and then and then process it according to the
3330 * type of the event and the opcode.
3331 */
3332 static void ixgbe_handle_fw_event(struct ixgbe_adapter *adapter)
3333 {
3334 struct ixgbe_aci_event event __cleanup(ixgbe_aci_event_cleanup);
3335 struct ixgbe_hw *hw = &adapter->hw;
3336 bool pending = false;
3337 int err;
3338
3339 if (adapter->flags2 & IXGBE_FLAG2_FW_ASYNC_EVENT)
3340 adapter->flags2 &= ~IXGBE_FLAG2_FW_ASYNC_EVENT;
3341 event.buf_len = IXGBE_ACI_MAX_BUFFER_SIZE;
3342 event.msg_buf = kzalloc(event.buf_len, GFP_KERNEL);
3343 if (!event.msg_buf)
3344 return;
3345
3346 do {
3347 err = ixgbe_aci_get_event(hw, &event, &pending);
3348 if (err)
3349 break;
3350
3351 switch (le16_to_cpu(event.desc.opcode)) {
3352 case ixgbe_aci_opc_get_link_status:
3353 ixgbe_handle_link_status_event(adapter, &event);
3354 break;
3355 case ixgbe_aci_opc_temp_tca_event:
3356 e_crit(drv, "%s\n", ixgbe_overheat_msg);
3357 ixgbe_down(adapter);
3358 break;
3359 case libie_aqc_opc_fw_logs_event:
> 3360 libie_get_fwlog_data(&hw->fwlog, event.msg_buf,
3361 le16_to_cpu(event.desc.datalen));
3362 break;
3363 default:
3364 e_warn(hw, "unknown FW async event captured\n");
3365 break;
3366 }
3367 } while (pending);
3368 }
3369
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-25 10:15 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=202508251750.6y0aVhmt-lkp@intel.com \
--to=lkp@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--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;
as well as URLs for NNTP newsgroup(s).