From: kernel test robot <lkp@intel.com>
To: Nicolas Saenz Julienne <nsaenzju@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Peter Zijlstra (Intel)" <peterz@infradead.org>
Subject: [nsaenz-rpi:ct-work-defer-wip 23/25] arch/x86/kernel/alternative.c:1186:47: error: 'CONTEXT_WORK_SYNC' undeclared
Date: Sat, 14 May 2022 13:36:16 +0800 [thread overview]
Message-ID: <202205141328.mnihXHJe-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git ct-work-defer-wip
head: ed63029652239a6befad96dd473b16332913f889
commit: d79e9aa1c1e3f664fff9d4e83500d7884777cad9 [23/25] context_tracking,x86: Fix text_poke_sync() vs NOHZ_FULL
config: i386-tinyconfig (https://download.01.org/0day-ci/archive/20220514/202205141328.mnihXHJe-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.2.0-20) 11.2.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git/commit/?id=d79e9aa1c1e3f664fff9d4e83500d7884777cad9
git remote add nsaenz-rpi https://git.kernel.org/pub/scm/linux/kernel/git/nsaenz/linux-rpi.git
git fetch --no-tags nsaenz-rpi ct-work-defer-wip
git checkout d79e9aa1c1e3f664fff9d4e83500d7884777cad9
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/kernel/ arch/x86/mm/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
arch/x86/kernel/alternative.c: In function 'do_sync_core_cond':
>> arch/x86/kernel/alternative.c:1186:47: error: 'CONTEXT_WORK_SYNC' undeclared (first use in this function)
1186 | CONTEXT_WORK_SYNC);
| ^~~~~~~~~~~~~~~~~
arch/x86/kernel/alternative.c:1186:47: note: each undeclared identifier is reported only once for each function it appears in
arch/x86/kernel/alternative.c:1187:1: error: control reaches end of non-void function [-Werror=return-type]
1187 | }
| ^
cc1: some warnings being treated as errors
vim +/CONTEXT_WORK_SYNC +1186 arch/x86/kernel/alternative.c
1182
1183 static bool do_sync_core_cond(int cpu, void *info)
1184 {
1185 return !context_tracking_set_cpu_work(cpu, CONTEXT_USER | CONTEXT_GUEST,
> 1186 CONTEXT_WORK_SYNC);
1187 }
1188
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-05-14 5:36 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=202205141328.mnihXHJe-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsaenzju@redhat.com \
--cc=peterz@infradead.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®