From: kernel test robot <lkp@intel.com>
To: "Pratyush Yadav (Google)" <pratyush@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
0day robot <lkp@intel.com>
Subject: include/linux/kexec_handover.h:129:1: error: expected identifier or '('
Date: Wed, 15 Jul 2026 16:10:20 +0200 [thread overview]
Message-ID: <202607151609.NMmZBoqm-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Pratyush-Yadav/kho-generalize-radix-tree-APIs/20260710-014638
head: a4ac1827ac09b0b27fd42c9776b5f5bae67530c8
commit: ff640ad9350077a3af2482f69c1e34ee82daeaa2 mm/mm_init: don't rely on memblock to get KHO scratch migratetype
date: 6 days ago
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260715/202607151609.NMmZBoqm-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260715/202607151609.NMmZBoqm-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/202607151609.NMmZBoqm-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/mm_init.c:33:
>> include/linux/kexec_handover.h:129:1: error: expected identifier or '('
129 | {
| ^
1 error generated.
vim +129 include/linux/kexec_handover.h
126
127 static inline void kho_init_scratch_migratetype(unsigned long start_pfn,
128 unsigned long end_pfn);
> 129 {
130 }
131 #endif /* CONFIG_KEXEC_HANDOVER */
132
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-15 14:10 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=202607151609.NMmZBoqm-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pratyush@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 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.