From: Ira Weiny <ira.weiny@intel.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Subject: [PATCH] cxl/cper: Fix non-ACPI-APEI-GHES build
Date: Wed, 01 May 2024 11:40:23 -0700 [thread overview]
Message-ID: <20240501-cper-fix-0day-v1-1-c0b0056eafbc@intel.com> (raw)
If ACPI_APEI_GHES is not configured the [un]register work functions are
not properly declared.
Fix copy paste error.
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
---
include/linux/cxl-event.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/cxl-event.h b/include/linux/cxl-event.h
index a0067c49e2ca..13090857c066 100644
--- a/include/linux/cxl-event.h
+++ b/include/linux/cxl-event.h
@@ -152,12 +152,12 @@ int cxl_cper_register_work(struct work_struct *work);
int cxl_cper_unregister_work(struct work_struct *work);
int cxl_cper_kfifo_get(struct cxl_cper_work_data *wd);
#else
-static inline int cxl_cper_register_work(struct work_struct *work);
+static inline int cxl_cper_register_work(struct work_struct *work)
{
return 0;
}
-static inline int cxl_cper_unregister_work(struct work_struct *work);
+static inline int cxl_cper_unregister_work(struct work_struct *work)
{
return 0;
}
---
base-commit: c19ac30eda3a1d14d4883de0ea214b6c5c96a9b4
change-id: 20240501-cper-fix-0day-c03ad861bbc3
Best regards,
--
Ira Weiny <ira.weiny@intel.com>
next reply other threads:[~2024-05-01 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 18:40 Ira Weiny [this message]
2024-05-01 18:51 ` [PATCH] cxl/cper: Fix non-ACPI-APEI-GHES build Dan Williams
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=20240501-cper-fix-0day-v1-1-c0b0056eafbc@intel.com \
--to=ira.weiny@intel.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=vishal.l.verma@intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).