From: kernel test robot <lkp@intel.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH RFC v2 2/3] firmware/efi: Process CXL Component Events
Date: Fri, 27 Oct 2023 08:05:51 +0800 [thread overview]
Message-ID: <202310270728.UjFWVMun-lkp@intel.com> (raw)
In-Reply-To: <20230601-cxl-cper-v2-2-314d9c36ab02@intel.com>
Hi Ira,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on 1c8b86a3799f7e5be903c3f49fcdaee29fd385b5]
url: https://github.com/intel-lab-lkp/linux/commits/Ira-Weiny/cxl-trace-Remove-uuid-from-event-trace-known-events/20231027-022447
base: 1c8b86a3799f7e5be903c3f49fcdaee29fd385b5
patch link: https://lore.kernel.org/r/20230601-cxl-cper-v2-2-314d9c36ab02%40intel.com
patch subject: [PATCH RFC v2 2/3] firmware/efi: Process CXL Component Events
config: x86_64-buildonly-randconfig-001-20231027 (https://download.01.org/0day-ci/archive/20231027/202310270728.UjFWVMun-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231027/202310270728.UjFWVMun-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/202310270728.UjFWVMun-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/firmware/efi/cper_cxl.c:218:5: error: redefinition of 'register_cxl_cper_notifier'
218 | int register_cxl_cper_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/firmware/efi/cper_cxl.h:13,
from drivers/firmware/efi/cper_cxl.c:11:
include/linux/efi.h:1409:19: note: previous definition of 'register_cxl_cper_notifier' with type 'int(struct notifier_block *)'
1409 | static inline int register_cxl_cper_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/firmware/efi/cper_cxl.c:224:6: error: redefinition of 'unregister_cxl_cper_notifier'
224 | void unregister_cxl_cper_notifier(struct notifier_block *nb)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/efi.h:1414:20: note: previous definition of 'unregister_cxl_cper_notifier' with type 'void(struct notifier_block *)'
1414 | static inline void unregister_cxl_cper_notifier(struct notifier_block *nb) { }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +/register_cxl_cper_notifier +218 drivers/firmware/efi/cper_cxl.c
217
> 218 int register_cxl_cper_notifier(struct notifier_block *nb)
219 {
220 return blocking_notifier_chain_register(&cxl_cper_chain_head, nb);
221 }
222 EXPORT_SYMBOL(register_cxl_cper_notifier);
223
> 224 void unregister_cxl_cper_notifier(struct notifier_block *nb)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-27 0:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 18:21 [PATCH RFC v2 0/3] efi/cxl-cper: Report CPER CXL component events through trace events Ira Weiny
2023-10-26 18:21 ` [PATCH RFC v2 1/3] cxl/trace: Remove uuid from event trace known events Ira Weiny
2023-10-26 20:55 ` Dan Williams
2023-10-30 16:58 ` Davidlohr Bueso
2023-10-26 18:21 ` [PATCH RFC v2 2/3] firmware/efi: Process CXL Component Events Ira Weiny
2023-10-26 21:02 ` Dan Williams
2023-10-31 16:46 ` Ira Weiny
2023-10-27 0:05 ` kernel test robot [this message]
2023-10-26 18:21 ` [PATCH RFC v2 3/3] cxl/memdev: Register for and process CPER events Ira Weiny
2023-10-26 22:19 ` kernel test robot
2023-10-26 22:56 ` Dan Williams
2023-10-31 17:13 ` Ira Weiny
2023-11-01 17:35 ` Jonathan Cameron
2023-10-27 2:32 ` kernel test robot
2023-10-30 21:03 ` Smita Koralahalli
2023-10-30 22:02 ` Dan Williams
2023-11-01 3:35 ` Ira Weiny
2023-11-01 21:59 ` Ira Weiny
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=202310270728.UjFWVMun-lkp@intel.com \
--to=lkp@intel.com \
--cc=ira.weiny@intel.com \
--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 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.