From: Ira Weiny <ira.weiny@intel.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>, <rafael@kernel.org>,
<lenb@kernel.org>, <james.morse@arm.com>, <tony.luck@intel.com>,
<bp@alien8.de>, <ira.weiny@intel.com>,
<Jonathan.Cameron@huawei.com>, <dan.j.williams@intel.com>,
<dave.jiang@intel.com>, <u.kleine-koenig@pengutronix.de>,
<xueshuai@linux.alibaba.com>, <shiju.jose@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Cc: <ruanjinjie@huawei.com>
Subject: Re: [PATCH -next 7/8] acpi/ghes: Make cxl_cper_fifo and cxl_cper_work static
Date: Wed, 21 Aug 2024 15:28:18 -0500 [thread overview]
Message-ID: <66c64de2b476a_1719d2942f@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20240819120055.3884953-1-ruanjinjie@huawei.com>
Jinjie Ruan wrote:
> The sparse tool complains as follows:
>
> drivers/acpi/apei/ghes.c:681:1: warning:
> symbol 'cxl_cper_fifo' was not declared. Should it be static?
>
> drivers/acpi/apei/ghes.c:685:20: warning:
> symbol 'cxl_cper_work' was not declared. Should it be static?
>
> These symbols are not used outside ghes.c, so marks them static.
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
> ---
> drivers/acpi/apei/ghes.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
> index 623cc0cb4a65..df31b3acaf0c 100644
> --- a/drivers/acpi/apei/ghes.c
> +++ b/drivers/acpi/apei/ghes.c
> @@ -678,11 +678,11 @@ static void ghes_defer_non_standard_event(struct acpi_hest_generic_data *gdata,
>
> /* Room for 8 entries for each of the 4 event log queues */
> #define CXL_CPER_FIFO_DEPTH 32
> -DEFINE_KFIFO(cxl_cper_fifo, struct cxl_cper_work_data, CXL_CPER_FIFO_DEPTH);
> +static DEFINE_KFIFO(cxl_cper_fifo, struct cxl_cper_work_data, CXL_CPER_FIFO_DEPTH);
>
> /* Synchronize schedule_work() with cxl_cper_work changes */
> static DEFINE_SPINLOCK(cxl_cper_work_lock);
> -struct work_struct *cxl_cper_work;
> +static struct work_struct *cxl_cper_work;
>
> static void cxl_cper_post_event(enum cxl_event_type event_type,
> struct cxl_cper_event_rec *rec)
> --
> 2.34.1
>
prev parent reply other threads:[~2024-08-21 20:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 12:00 [PATCH -next 7/8] acpi/ghes: Make cxl_cper_fifo and cxl_cper_work static Jinjie Ruan
2024-08-21 20:28 ` Ira Weiny [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=66c64de2b476a_1719d2942f@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tony.luck@intel.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=xueshuai@linux.alibaba.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