From: kernel test robot <lkp@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [daveh-devel:old-ucode-platform 2/6] include/linux/../../arch/x86/include/asm/intel-family.h:5:10: fatal error: 'asm/vfm.h' file not found
Date: Tue, 25 Nov 2025 12:33:26 +0800 [thread overview]
Message-ID: <202511251209.Y78F7F9p-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git old-ucode-platform
head: 13bb70ba267344f42129e7942104f056d44389b5
commit: 61c21b2d8b57e9b2d48b774618c1bd19ce7a3a59 [2/6] x86/cpu: Add missing #include
config: loongarch-allmodconfig (https://download.01.org/0day-ci/archive/20251125/202511251209.Y78F7F9p-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251125/202511251209.Y78F7F9p-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/202511251209.Y78F7F9p-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/peci/device.c:6:
In file included from include/linux/peci-cpu.h:33:
>> include/linux/../../arch/x86/include/asm/intel-family.h:5:10: fatal error: 'asm/vfm.h' file not found
5 | #include <asm/vfm.h>
| ^~~~~~~~~~~
1 error generated.
vim +5 include/linux/../../arch/x86/include/asm/intel-family.h
4
> 5 #include <asm/vfm.h>
6
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-11-25 4:34 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=202511251209.Y78F7F9p-lkp@intel.com \
--to=lkp@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox