From: kernel test robot <lkp@intel.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dwmw2:hardpps-filter-p3-wip 7/8] kernel/time/ntp.c:175:9: error: implicit declaration of function 'pps_fit_reset'
Date: Mon, 05 Oct 2026 14:35:42 +0800 [thread overview]
Message-ID: <202610051451.E6GGdAVP-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/dwmw2/linux hardpps-filter-p3-wip
head: 24b5bb6499c7dcc715bf50f768bc24b50f9cc631
commit: f04f156f18471fef43c99e5ef017165b43f34e7a [7/8] ntp: Estimate PPS frequency by least-squares fit over the interval
config: m68k-defconfig (https://download.01.org/0day-ci/archive/20261005/202610051451.E6GGdAVP-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261005/202610051451.E6GGdAVP-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/202610051451.E6GGdAVP-lkp@intel.com/
All error/warnings (new ones prefixed by >>):
kernel/time/ntp.c: In function 'pps_clear':
>> kernel/time/ntp.c:175:9: error: implicit declaration of function 'pps_fit_reset' [-Wimplicit-function-declaration]
175 | pps_fit_reset(ntpdata);
| ^~~~~~~~~~~~~
kernel/time/ntp.c: At top level:
>> kernel/time/ntp.c:1244:13: warning: conflicting types for 'pps_fit_reset'; have 'void(struct ntp_data *)'
1244 | static void pps_fit_reset(struct ntp_data *ntpdata)
| ^~~~~~~~~~~~~
>> kernel/time/ntp.c:1244:13: error: static declaration of 'pps_fit_reset' follows non-static declaration
kernel/time/ntp.c:175:9: note: previous implicit declaration of 'pps_fit_reset' with type 'void(struct ntp_data *)'
175 | pps_fit_reset(ntpdata);
| ^~~~~~~~~~~~~
vim +/pps_fit_reset +175 kernel/time/ntp.c
162
163 /**
164 * pps_clear - Clears the PPS state variables
165 * @ntpdata: Pointer to ntp data
166 */
167 static inline void pps_clear(struct ntp_data *ntpdata)
168 {
169 pps_reset_freq_interval(ntpdata);
170 ntpdata->pps_tf[0] = 0;
171 ntpdata->pps_tf[1] = 0;
172 ntpdata->pps_tf[2] = 0;
173 ntpdata->pps_fbase.tv_sec = ntpdata->pps_fbase.tv_nsec = 0;
174 ntpdata->pps_rawring_n = 0;
> 175 pps_fit_reset(ntpdata);
176 ntpdata->pps_freq = 0;
177 }
178
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-05 6: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=202610051451.E6GGdAVP-lkp@intel.com \
--to=lkp@intel.com \
--cc=dwmw@amazon.co.uk \
--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.