From: Heinz Mauelshagen <heinzm@redhat.com>
To: dm-devel@redhat.com
Subject: Re: [PATCH -next] dm integrity: Make dm_integrity_init and dm_integrity_exit static
Date: Fri, 22 Mar 2019 15:56:09 +0100 [thread overview]
Message-ID: <a238ebca-7e1a-e3e0-ea3a-79cd0135b6e0@redhat.com> (raw)
In-Reply-To: <20190322141634.20664-1-yuehaibing@huawei.com>
On 3/22/19 3:16 PM, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> Fix sparse warnings:
>
> drivers/md/dm-integrity.c:3619:12: warning:
> symbol 'dm_integrity_init' was not declared. Should it be static?
> drivers/md/dm-integrity.c:3638:6: warning:
> symbol 'dm_integrity_exit' was not declared. Should it be static?
Yes, both should be static.
Once on it, declare 'static void __exit dm_integrity_exit(void);'
Heinz
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
> ---
> drivers/md/dm-integrity.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/md/dm-integrity.c b/drivers/md/dm-integrity.c
> index d57d997..0932c32 100644
> --- a/drivers/md/dm-integrity.c
> +++ b/drivers/md/dm-integrity.c
> @@ -3616,7 +3616,7 @@ static struct target_type integrity_target = {
> .io_hints = dm_integrity_io_hints,
> };
>
> -int __init dm_integrity_init(void)
> +static int __init dm_integrity_init(void)
> {
> int r;
>
> @@ -3635,7 +3635,7 @@ int __init dm_integrity_init(void)
> return r;
> }
>
> -void dm_integrity_exit(void)
> +static void dm_integrity_exit(void)
> {
> dm_unregister_target(&integrity_target);
> kmem_cache_destroy(journal_io_cache);
prev parent reply other threads:[~2019-03-22 14:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 14:16 [PATCH -next] dm integrity: Make dm_integrity_init and dm_integrity_exit static Yue Haibing
2019-03-22 14:56 ` Heinz Mauelshagen [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=a238ebca-7e1a-e3e0-ea3a-79cd0135b6e0@redhat.com \
--to=heinzm@redhat.com \
--cc=dm-devel@redhat.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