From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mariusz Gorski <marius.gorski@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
Andreas Dilger <andreas.dilger@intel.com>,
Peng Tao <bergwolf@gmail.com>,
devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] staging: lustre: Reduce function visibility
Date: Wed, 29 Oct 2014 16:35:10 +0800 [thread overview]
Message-ID: <20141029083510.GA31558@kroah.com> (raw)
In-Reply-To: <1414200638-20682-2-git-send-email-marius.gorski@gmail.com>
On Sat, Oct 25, 2014 at 03:30:37AM +0200, Mariusz Gorski wrote:
> This patch fixes the following sparse warnings:
> drivers/staging/lustre/lnet/lnet/module.c:47:1: warning: symbol
> 'lnet_configure' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/module.c:67:1: warning: symbol
> 'lnet_unconfigure' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/module.c:87:1: warning: symbol
> 'lnet_ioctl' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/module.c:114:1: warning: symbol
> 'init_lnet' was not declared. Should it be static?
> drivers/staging/lustre/lnet/lnet/module.c:139:1: warning: symbol
> 'fini_lnet' was not declared. Should it be static?
>
> Signed-off-by: Mariusz Gorski <marius.gorski@gmail.com>
> ---
> drivers/staging/lustre/lnet/lnet/module.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/lustre/lnet/lnet/module.c b/drivers/staging/lustre/lnet/lnet/module.c
> index e84d59d..dc09b43 100644
> --- a/drivers/staging/lustre/lnet/lnet/module.c
> +++ b/drivers/staging/lustre/lnet/lnet/module.c
> @@ -43,7 +43,7 @@ MODULE_PARM_DESC(config_on_load, "configure network at module load");
>
> static struct mutex lnet_config_mutex;
>
> -int
> +static int
> lnet_configure(void *arg)
> {
> /* 'arg' only there so I can be passed to cfs_create_thread() */
> @@ -63,7 +63,7 @@ lnet_configure(void *arg)
> return rc;
> }
>
> -int
> +static int
> lnet_unconfigure(void)
> {
> int refcount;
> @@ -83,7 +83,7 @@ lnet_unconfigure(void)
> return (refcount == 0) ? 0 : -EBUSY;
> }
>
> -int
> +static int
> lnet_ioctl(unsigned int cmd, struct libcfs_ioctl_data *data)
> {
> int rc;
> @@ -110,7 +110,7 @@ lnet_ioctl(unsigned int cmd, struct libcfs_ioctl_data *data)
>
> DECLARE_IOCTL_HANDLER(lnet_ioctl_handler, lnet_ioctl);
>
> -int
> +static int
> init_lnet(void)
> {
> int rc;
> @@ -135,7 +135,7 @@ init_lnet(void)
> return 0;
> }
>
> -void
> +static void
> fini_lnet(void)
> {
> int rc;
Someone did this patch before you, sorry.
greg k-h
next prev parent reply other threads:[~2014-10-29 15:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 1:30 [PATCH v2 0/2] staging: lustre: Minor lnet module cleanup Mariusz Gorski
2014-10-25 1:30 ` [PATCH v2 1/2] staging: lustre: Reduce function visibility Mariusz Gorski
2014-10-29 8:35 ` Greg Kroah-Hartman [this message]
2014-10-25 1:30 ` [PATCH v2 2/2] staging: lustre: Use __init and __exit markers for lifecycle functions Mariusz Gorski
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=20141029083510.GA31558@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.dilger@intel.com \
--cc=bergwolf@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.gorski@gmail.com \
--cc=oleg.drokin@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