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-soak 16/23] Warning: kernel/time/ntp.c:99 struct member 'pps_rawring' not described in 'ntp_data'
Date: Mon, 05 Oct 2026 11:57:16 +0800 [thread overview]
Message-ID: <202610051140.ICEZtkyQ-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/dwmw2/linux hardpps-filter-soak
head: eef47b09d53ef553d3089bce6c9a0f6a9c792f29
commit: d988e07afea778f8ca133be682f4d3710ac32736 [16/23] ntp: Select least-delayed of recent pulses as PPS frequency endpoints
config: sparc-allnoconfig (https://download.01.org/0day-ci/archive/20261005/202610051140.ICEZtkyQ-lkp@intel.com/config)
compiler: sparc-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261005/202610051140.ICEZtkyQ-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/202610051140.ICEZtkyQ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/time/ntp.c:99 struct member 'pps_rawring' not described in 'ntp_data'
>> Warning: kernel/time/ntp.c:99 struct member 'pps_rawring_n' not described in 'ntp_data'
Warning: kernel/time/ntp.c:591 function parameter 'ntpdata' not described in 'ntp_update_skew_delta'
Warning: kernel/time/ntp.c:591 function parameter 'settle' not described in 'ntp_update_skew_delta'
Warning: kernel/time/ntp.c:591 expecting prototype for ntp_set_time_offset(). Prototype was for ntp_update_skew_delta() instead
>> Warning: kernel/time/ntp.c:99 struct member 'pps_rawring' not described in 'ntp_data'
>> Warning: kernel/time/ntp.c:99 struct member 'pps_rawring_n' not described in 'ntp_data'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-05 3: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=202610051140.ICEZtkyQ-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.