From: kernel test robot <lkp@intel.com>
To: aubrey.li@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [anolis-intel-cloud:intel-6.6-CWF-PLR-ANBZ26486 11/11] drivers/net/ethernet/netronome/nfp/nfp_main.c:1128:6: warning: no previous prototype for 'nfp_pci_error_reset_prepare'
Date: Tue, 16 Dec 2025 00:24:39 +0800 [thread overview]
Message-ID: <202512160003.ZEouzSvr-lkp@intel.com> (raw)
tree: https://gitee.com/anolis/intel-cloud-kernel.git intel-6.6-CWF-PLR-ANBZ26486
head: 0bcb74c919819123b737554f5d35edefa0555d65
commit: c3f08cf3e17600da0dcf2c945de2287b1ea616ff [11/11] anolis: nfp: add pci_error_handler callback
config: x86_64-allmodconfig (https://download.01.org/0day-ci/archive/20251216/202512160003.ZEouzSvr-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/20251216/202512160003.ZEouzSvr-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/202512160003.ZEouzSvr-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/net/ethernet/netronome/nfp/nfp_main.c:1128:6: warning: no previous prototype for 'nfp_pci_error_reset_prepare' [-Wmissing-prototypes]
1128 | void nfp_pci_error_reset_prepare(struct pci_dev *dev)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/net/ethernet/netronome/nfp/nfp_main.c:1144:6: warning: no previous prototype for 'nfp_pci_error_reset_done' [-Wmissing-prototypes]
1144 | void nfp_pci_error_reset_done(struct pci_dev *dev)
| ^~~~~~~~~~~~~~~~~~~~~~~~
vim +/nfp_pci_error_reset_prepare +1128 drivers/net/ethernet/netronome/nfp/nfp_main.c
1127
> 1128 void nfp_pci_error_reset_prepare(struct pci_dev *dev)
1129 {
1130 struct nfp_pf *pf = pci_get_drvdata(dev);
1131
1132 if (pf) {
1133 if (pf->multi_pf.en && pf->multi_pf.beat_addr) {
1134 /* Pause heartbeat timer so it can't happen during FLR */
1135 del_timer_sync(&pf->multi_pf.beat_timer);
1136 /* We need to write keepalive to keep firmware alive
1137 * during frequent FLR.
1138 */
1139 writeq(jiffies, nfp_get_beat_addr(pf, pf->multi_pf.id));
1140 }
1141 }
1142 }
1143
> 1144 void nfp_pci_error_reset_done(struct pci_dev *dev)
1145 {
1146 struct nfp_pf *pf = pci_get_drvdata(dev);
1147
1148 if (pf)
1149 if (pf->multi_pf.en && pf->multi_pf.beat_addr)
1150 add_timer(&pf->multi_pf.beat_timer);
1151 }
1152
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-15 16:25 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=202512160003.ZEouzSvr-lkp@intel.com \
--to=lkp@intel.com \
--cc=aubrey.li@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.