From: kernel test robot <lkp@intel.com>
To: Jacob Keller <jacob.e.keller@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>,
Wojciech Drewek <wojciech.drewek@intel.com>,
Rahul Rameshbabu <rrameshbabu@nvidia.com>,
Sunil Goutham <sgoutham@marvell.com>,
Simon Horman <horms@kernel.org>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>
Subject: [Intel-wired-lan] [tnguy-next-queue:dev-queue 67/85] iavf_main.c:undefined reference to `iavf_ptp_cap_supported'
Date: Tue, 5 Nov 2024 14:57:04 +0800 [thread overview]
Message-ID: <202411051410.QeBCuZ5y-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
head: 676d779106de51fc4e2685ca8de610ee5a70d35f
commit: adcff768e70df6a1905ffe1387259da00b859521 [67/85] iavf: add support for Rx timestamps to hotpath
config: parisc-randconfig-001-20241105 (https://download.01.org/0day-ci/archive/20241105/202411051410.QeBCuZ5y-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241105/202411051410.QeBCuZ5y-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/202411051410.QeBCuZ5y-lkp@intel.com/
All errors (new ones prefixed by >>):
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_main.o: in function `iavf_hwstamp_set':
iavf_main.c:(.text+0x1924): undefined reference to `iavf_ptp_set_ts_config'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_main.o: in function `iavf_configure':
>> iavf_main.c:(.text+0x61ac): undefined reference to `iavf_ptp_cap_supported'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_main.o: in function `iavf_remove':
iavf_main.c:(.text+0x73cc): undefined reference to `iavf_ptp_release'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_main.o: in function `iavf_init_config_adapter':
iavf_main.c:(.text+0x8594): undefined reference to `iavf_ptp_init'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_virtchnl.o: in function `iavf_configure_queues':
drivers/net/ethernet/intel/iavf/iavf_virtchnl.c:381:(.text+0xf08): undefined reference to `iavf_ptp_cap_supported'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_virtchnl.o: in function `iavf_virtchnl_completion':
drivers/net/ethernet/intel/iavf/iavf_virtchnl.c:2710:(.text+0x4778): undefined reference to `iavf_ptp_process_caps'
hppa-linux-ld: drivers/net/ethernet/intel/iavf/iavf_txrx.o: in function `iavf_process_skb_fields':
>> drivers/net/ethernet/intel/iavf/iavf_txrx.c:1111:(.text+0x185c): undefined reference to `iavf_ptp_extend_32b_timestamp'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-05 6:57 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=202411051410.QeBCuZ5y-lkp@intel.com \
--to=lkp@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rrameshbabu@nvidia.com \
--cc=sgoutham@marvell.com \
--cc=wojciech.drewek@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