From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh (Schneider Electric)"
<thomas.weissschuh@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/auxclock-nanosleep 17/41] Warning: kernel/time/timekeeping.c:241 expecting prototype for ktime_mono_to_aux(). Prototype was for ktime_aux_to_mono() instead
Date: Sat, 24 Oct 2026 01:29:05 +0800 [thread overview]
Message-ID: <202610240145.XHPPRoyD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/auxclock-nanosleep
head: a40991dd87115c3f70bf87884b803ed7e09dc387
commit: 43397fe79e1c3dcc1334df0cd2c26459efad86ba [17/41] timekeeping: Add facilities to convert between monotonic and auxiliary clock timestamps
config: csky-allnoconfig (https://download.01.org/0day-ci/archive/20261024/202610240145.XHPPRoyD-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 16.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261024/202610240145.XHPPRoyD-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/202610240145.XHPPRoyD-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: kernel/time/timekeeping.c:241 expecting prototype for ktime_mono_to_aux(). Prototype was for ktime_aux_to_mono() instead
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-23 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:29 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-23 11:47 [thomas-weissschuh:b4/auxclock-nanosleep 17/41] Warning: kernel/time/timekeeping.c:241 expecting prototype for ktime_mono_to_aux(). Prototype was for ktime_aux_to_mono() instead kernel test robot
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=202610240145.XHPPRoyD-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=thomas.weissschuh@linutronix.de \
/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.