From: kernel test robot <lkp@intel.com>
To: vishnu singh <v-singh1@ti.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
Date: Sun, 24 Aug 2025 12:35:28 +0800 [thread overview]
Message-ID: <202508241207.pLPFn1Tw-lkp@intel.com> (raw)
In-Reply-To: <20250823044034.189939-1-v-singh1@ti.com>
Hi vishnu,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20250822]
[also build test ERROR on v6.17-rc2]
[cannot apply to arm64/for-next/core akpm-mm/mm-everything linus/master v6.17-rc2 v6.17-rc1 v6.16]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/vishnu-singh/time-introduce-BOOT_TIME_TRACKER-and-minimal-boot-timestamp/20250823-124230
base: next-20250822
patch link: https://lore.kernel.org/r/20250823044034.189939-1-v-singh1%40ti.com
patch subject: [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20250824/202508241207.pLPFn1Tw-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250824/202508241207.pLPFn1Tw-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/202508241207.pLPFn1Tw-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/time/boot_time_now.c:4:10: fatal error: asm/boot_time_primitives.h: No such file or directory
4 | #include <asm/boot_time_primitives.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +4 kernel/time/boot_time_now.c
2
3 #include <linux/boot_time_now.h>
> 4 #include <asm/boot_time_primitives.h>
5
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-24 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 4:40 [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp vishnu singh
2025-08-23 22:53 ` Thomas Gleixner
2025-08-23 23:12 ` Thomas Gleixner
2025-09-01 4:05 ` Kaiwan N Billimoria
2025-09-01 5:57 ` Kaiwan N Billimoria
2025-09-02 7:02 ` [RFC PATCH] time: introduce BOOT_TIME_TRACKER and minimal boot timestamp Kaiwan N Billimoria
2025-09-02 10:52 ` Thomas Gleixner
2025-09-02 13:39 ` Kaiwan N Billimoria
2025-09-02 21:32 ` Thomas Gleixner
2025-08-24 4:35 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-23 4:19 vishnu singh
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=202508241207.pLPFn1Tw-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=v-singh1@ti.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 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.