From: kernel test robot <lkp@intel.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [weiny2:cxl-cper-testing 5/5] include/linux/cxl-event.h:158:1: error: expected identifier or '('
Date: Thu, 2 May 2024 09:17:39 +0800 [thread overview]
Message-ID: <202405020910.9Co46x8J-lkp@intel.com> (raw)
tree: https://github.com/weiny2/linux-kernel.git cxl-cper-testing
head: 9561664438db543f4d61ee0dde4fa9722239fb13
commit: 9561664438db543f4d61ee0dde4fa9722239fb13 [5/5] acpi/ghes: Add CXL CPER injection debugfs
config: i386-buildonly-randconfig-003-20240501 (https://download.01.org/0day-ci/archive/20240502/202405020910.9Co46x8J-lkp@intel.com/config)
compiler: clang version 18.1.4 (https://github.com/llvm/llvm-project e6c3289804a67ea0bb6a86fadbe454dd93b8d855)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240502/202405020910.9Co46x8J-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/202405020910.9Co46x8J-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/acpi/acpi_extlog.c:19:
In file included from drivers/acpi/apei/apei-internal.h:11:
>> include/linux/cxl-event.h:158:1: error: expected identifier or '('
158 | {
| ^
include/linux/cxl-event.h:163:1: error: expected identifier or '('
163 | {
| ^
2 errors generated.
vim +158 include/linux/cxl-event.h
f64693ceeed628 Ira Weiny 2023-07-13 151
f64693ceeed628 Ira Weiny 2023-07-13 152 #ifdef CONFIG_ACPI_APEI_GHES
f64693ceeed628 Ira Weiny 2023-07-13 153 int cxl_cper_register_work(struct work_struct *work);
f64693ceeed628 Ira Weiny 2023-07-13 154 int cxl_cper_unregister_work(struct work_struct *work);
f64693ceeed628 Ira Weiny 2023-07-13 155 int cxl_cper_kfifo_get(struct cxl_cper_work_data *wd);
f64693ceeed628 Ira Weiny 2023-07-13 156 #else
f64693ceeed628 Ira Weiny 2023-07-13 157 static inline int cxl_cper_register_work(struct work_struct *work);
f64693ceeed628 Ira Weiny 2023-07-13 @158 {
f64693ceeed628 Ira Weiny 2023-07-13 159 return 0;
f64693ceeed628 Ira Weiny 2023-07-13 160 }
f64693ceeed628 Ira Weiny 2023-07-13 161
:::::: The code at line 158 was first introduced by commit
:::::: f64693ceeed628d8036c8ac75f655bb3292d5bcf acpi/ghes: Process CXL Component Events
:::::: TO: Ira Weiny <ira.weiny@intel.com>
:::::: CC: Ira Weiny <ira.weiny@intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-05-02 1:18 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=202405020910.9Co46x8J-lkp@intel.com \
--to=lkp@intel.com \
--cc=ira.weiny@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