From: Corey Minyard <minyard@acm.org>
To: Wei Yongjun <weiyongjun1@huawei.com>
Cc: Ioanna Alifieraki <ioanna-maria.alifieraki@canonical.com>,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Hulk Robot <hulkci@huawei.com>
Subject: Re: [PATCH -next] ipmi: msghandler: Make symbol 'remove_work_wq' static
Date: Tue, 23 Nov 2021 06:45:14 -0600 [thread overview]
Message-ID: <20211123124514.GT15676@minyard.net> (raw)
In-Reply-To: <20211123083618.2366808-1-weiyongjun1@huawei.com>
On Tue, Nov 23, 2021 at 08:36:18AM +0000, Wei Yongjun wrote:
> The sparse tool complains as follows:
>
> drivers/char/ipmi/ipmi_msghandler.c:194:25: warning:
> symbol 'remove_work_wq' was not declared. Should it be static?
>
> This symbol is not used outside of ipmi_msghandler.c, so
> marks it static.
Thanks, I should have noticed this.
-corey
>
> Fixes: 1d49eb91e86e ("ipmi: Move remove_work to dedicated workqueue")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index 1ade72bfae0f..a2ec0171363a 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -191,7 +191,7 @@ struct ipmi_user {
> struct work_struct remove_work;
> };
>
> -struct workqueue_struct *remove_work_wq;
> +static struct workqueue_struct *remove_work_wq;
>
> static struct ipmi_user *acquire_ipmi_user(struct ipmi_user *user, int *index)
> __acquires(user->release_barrier)
>
prev parent reply other threads:[~2021-11-23 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 8:36 [PATCH -next] ipmi: msghandler: Make symbol 'remove_work_wq' static Wei Yongjun
2021-11-23 12:45 ` Corey Minyard [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=20211123124514.GT15676@minyard.net \
--to=minyard@acm.org \
--cc=hulkci@huawei.com \
--cc=ioanna-maria.alifieraki@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=weiyongjun1@huawei.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 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.