From: Gao Xiang <gaoxiang25@huawei.com>
To: Bo YU <tsu.yubo@gmail.com>
Cc: <yuchao0@huawei.com>, <gregkh@linuxfoundation.org>,
<yuzibode@126.com>, <linux-erofs@lists.ozlabs.org>,
<devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>,
Miao Xie <miaoxie@huawei.com>,
"fangwei (I)" <fangwei1@huawei.com>
Subject: Re: [PATCH] staging/erofs: fix sparse's warnings on undeclared symbols in erofs
Date: Thu, 21 Feb 2019 22:35:01 +0800 [thread overview]
Message-ID: <05254fc6-6bd7-7c30-cfcc-2ddff4ac13b6@huawei.com> (raw)
In-Reply-To: <20190221142845.13604-1-tsu.yubo@gmail.com>
Hi Bo,
On 2019/2/21 22:28, Bo YU wrote:
> From: Bo Yu <tsu.yubo@gmail.com>
>
> Fix sparse warnings:
>
> drivers/staging/erofs/utils.c:134:6: warning: symbol
> 'erofs_try_to_release_workgroup' was not declared. Should it be static?
>
> Fixes: 51232df5e4b26("staging: erofs: fix race when the managed cache is enabled")
> Cc: Gao Xiang <gaoxiang25@huawei.com>
> Cc: Chao Yu <yuchao0@huawei.com>
> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Bo Yu <tsu.yubo@gmail.com>
> ---
> drivers/staging/erofs/utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/erofs/utils.c b/drivers/staging/erofs/utils.c
> index b535898ca753..33cd5ad55cb8 100644
> --- a/drivers/staging/erofs/utils.c
> +++ b/drivers/staging/erofs/utils.c
> @@ -131,7 +131,7 @@ static void erofs_workgroup_unfreeze_final(struct erofs_workgroup *grp)
> __erofs_workgroup_free(grp);
> }
>
> -bool erofs_try_to_release_workgroup(struct erofs_sb_info *sbi,
> +static bool erofs_try_to_release_workgroup(struct erofs_sb_info *sbi,
> struct erofs_workgroup *grp,
> bool cleanup)
> {
>
Have you looked the latest kernel code?
It seems erofs_try_to_release_workgroup is already be claimed as static...
See:
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/erofs/utils.c?h=staging-next#n148
Thanks,
Gao Xiang
next prev parent reply other threads:[~2019-02-21 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 14:28 Bo YU
2019-02-21 14:35 ` Gao Xiang [this message]
2019-02-22 0:57 ` YU Bo
2019-02-22 1:28 ` Gao Xiang
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=05254fc6-6bd7-7c30-cfcc-2ddff4ac13b6@huawei.com \
--to=gaoxiang25@huawei.com \
--cc=devel@driverdev.osuosl.org \
--cc=fangwei1@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=tsu.yubo@gmail.com \
--cc=yuchao0@huawei.com \
--cc=yuzibode@126.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
all inboxes | Powered by JetHome®