From: Xin Li <xin@zytor.com>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 1/3] x86/fred: Allow variable-sized event frame
Date: Wed, 19 Mar 2025 22:43:13 -0700 [thread overview]
Message-ID: <0fc86279-296e-4d61-bf24-fa9cb2f10629@zytor.com> (raw)
In-Reply-To: <202503200325.iKcHqUsb-lkp@intel.com>
On 3/19/2025 12:45 PM, kernel test robot wrote:
> Hi Xin,
>
> kernel test robot noticed the following build errors:
>
> [auto build test ERROR on 60c162a51180cb2b05d7505a565ab079bfa9cf12]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Xin-Li-Intel/x86-fred-Allow-variable-sized-event-frame/20250319-151307
> base: 60c162a51180cb2b05d7505a565ab079bfa9cf12
> patch link: https://lore.kernel.org/r/20250319071009.1390984-2-xin%40zytor.com
> patch subject: [PATCH v3 1/3] x86/fred: Allow variable-sized event frame
> config: i386-buildonly-randconfig-003-20250320 (https://download.01.org/0day-ci/archive/20250320/202503200325.iKcHqUsb-lkp@intel.com/config)
> compiler: clang version 20.1.0 (https://github.com/llvm/llvm-project 24a30daaa559829ad079f2ff7f73eb4e18095f88)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250320/202503200325.iKcHqUsb-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/202503200325.iKcHqUsb-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>>> init/init_task.c:68:17: error: use of undeclared identifier '__top_init_kernel_stack'
> 68 | .thread_info = INIT_THREAD_INFO(init_task),
> | ^
> arch/x86/include/asm/thread_info.h:76:36: note: expanded from macro 'INIT_THREAD_INFO'
> 76 | .user_pt_regs = (struct pt_regs *)__top_init_kernel_stack, \
> | ^
> 1 error generated.
>
Okay, I need to add:
extern unsigned long __top_init_kernel_stack[];
Unfortunately my configs don't expose the build issue.
Thanks!
Xin
prev parent reply other threads:[~2025-03-20 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250319071009.1390984-2-xin@zytor.com>
2025-03-19 19:45 ` [PATCH v3 1/3] x86/fred: Allow variable-sized event frame kernel test robot
2025-03-20 5:43 ` Xin Li [this message]
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=0fc86279-296e-4d61-bf24-fa9cb2f10629@zytor.com \
--to=xin@zytor.com \
--cc=lkp@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