From: kernel test robot <lkp@intel.com>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-s390@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Andreas Grapentin <gra@linux.ibm.com>,
"Nina Schoetterl-Glausch" <nsg@linux.ibm.com>,
Gautam Gala <ggala@linux.ibm.com>
Subject: [kvms390:queue 20/21] arch/arm64/include/asm/sysreg.h:182:10: fatal error: asm/sysreg-defs.h: No such file or directory
Date: Thu, 15 Oct 2026 03:34:10 +0800 [thread overview]
Message-ID: <202610150332.4CegXzzq-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git queue
head: 74153e116543bc017aff93720fcc603cb0e8598c
commit: 325380d8e78936b65d30e29d6be478bdd03c87d8 [20/21] KVM: s390: arm64: Integrate arm on s390
config: s390-debug_defconfig (https://download.01.org/0day-ci/archive/20261015/202610150332.4CegXzzq-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261015/202610150332.4CegXzzq-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/202610150332.4CegXzzq-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/s390/include/arm64/sysreg.h:11,
from arch/s390/include/arm64/ptrace.h:6,
from arch/arm64/include/uapi/asm/kvm.h:37,
from arch/s390/include/asm/kvm.h:3,
from include/uapi/linux/kvm.h:16,
from include/linux/kvm_host.h:40,
from arch/s390/kvm/arm64/handle_exit.c:3:
>> arch/arm64/include/asm/sysreg.h:182:10: fatal error: asm/sysreg-defs.h: No such file or directory
182 | #include "asm/sysreg-defs.h"
| ^~~~~~~~~~~~~~~~~~~
compilation terminated.
vim +182 arch/arm64/include/asm/sysreg.h
7c9cb893ae3e06c Marc Zyngier 2025-04-25 175
c07d8017bceb82c Mark Brown 2022-05-03 176 /*
c07d8017bceb82c Mark Brown 2022-05-03 177 * Automatically generated definitions for system registers, the
c07d8017bceb82c Mark Brown 2022-05-03 178 * manual encodings below are in the process of being converted to
c07d8017bceb82c Mark Brown 2022-05-03 179 * come from here. The header relies on the definition of sys_reg()
c07d8017bceb82c Mark Brown 2022-05-03 180 * earlier in this file.
c07d8017bceb82c Mark Brown 2022-05-03 181 */
c07d8017bceb82c Mark Brown 2022-05-03 @182 #include "asm/sysreg-defs.h"
c07d8017bceb82c Mark Brown 2022-05-03 183
:::::: The code at line 182 was first introduced by commit
:::::: c07d8017bceb82cbe5fedd129d072c59a53f5513 arm64/sysreg: Enable automatic generation of system register definitions
:::::: TO: Mark Brown <broonie@kernel.org>
:::::: CC: Catalin Marinas <catalin.marinas@arm.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-14 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 19:34 kernel test robot [this message]
2026-10-15 8:15 ` [kvms390:queue 20/21] arch/arm64/include/asm/sysreg.h:182:10: fatal error: asm/sysreg-defs.h: No such file or directory Steffen Eiden
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=202610150332.4CegXzzq-lkp@intel.com \
--to=lkp@intel.com \
--cc=borntraeger@linux.ibm.com \
--cc=ggala@linux.ibm.com \
--cc=gra@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=nsg@linux.ibm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=seiden@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox