From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: [tip:timers/vdso 33/41] arch/x86/include/asm/vdso/vsyscall.h:16:10: fatal error: asm/vvar.h: No such file or directory
Date: Sat, 2 Nov 2024 20:30:42 +0800 [thread overview]
Message-ID: <202411022036.pBj9Jefz-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/vdso
head: 3bf96deae5ad9664bdf2db95599e52221f9ddc33
commit: 915c1d9df1f757b0979283b6e50da9b3ccc4d826 [33/41] x86/vdso: Split virtual clock pages into dedicated mapping
config: x86_64-rhel-8.3 (https://download.01.org/0day-ci/archive/20241102/202411022036.pBj9Jefz-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241102/202411022036.pBj9Jefz-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/202411022036.pBj9Jefz-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/x86/entry/vdso/vma.c:27:
>> arch/x86/include/asm/vdso/vsyscall.h:16:10: fatal error: asm/vvar.h: No such file or directory
16 | #include <asm/vvar.h>
| ^~~~~~~~~~~~
compilation terminated.
vim +16 arch/x86/include/asm/vdso/vsyscall.h
7ac8707479886c Vincenzo Frascino 2019-06-21 13
7ac8707479886c Vincenzo Frascino 2019-06-21 14 #include <vdso/datapage.h>
7ac8707479886c Vincenzo Frascino 2019-06-21 15 #include <asm/vgtod.h>
7ac8707479886c Vincenzo Frascino 2019-06-21 @16 #include <asm/vvar.h>
7ac8707479886c Vincenzo Frascino 2019-06-21 17
:::::: The code at line 16 was first introduced by commit
:::::: 7ac8707479886c75f353bfb6a8273f423cfccb23 x86/vdso: Switch to generic vDSO implementation
:::::: TO: Vincenzo Frascino <vincenzo.frascino@arm.com>
:::::: CC: Thomas Gleixner <tglx@linutronix.de>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-02 12:31 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=202411022036.pBj9Jefz-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®