public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Zapalowicz <bergo.torino@gmail.com>
To: Serguey Parkhomovsky <sergueyparkhomovsky@gmail.com>
Cc: Oleg Drokin <oleg.drokin@intel.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] staging: lustre: linux-prim.c: fix sparse warnings about static declaration
Date: Wed, 31 Dec 2014 11:40:29 +0100	[thread overview]
Message-ID: <20141231104029.GA25819@t400> (raw)
In-Reply-To: <20141231084833.GA6643@fedora.localdomain>

On 12/31, Serguey Parkhomovsky wrote:
> Fixes the following sparse warnings:
> 
> drivers/staging/lustre/lustre/libcfs/linux/linux-prim.c:198:1: warning: symbol 'libcfs_arch_init' was not declared. Should it be static?
> drivers/staging/lustre/lustre/libcfs/linux/linux-prim.c:204:1: warning: symbol 'libcfs_arch_cleanup' was not declared. Should it be static?

This lines are way too long. You should break the commit message line
around 72nd column so that it looks nice when emailed.

You can also omit the filename from the topic line as this is already in
the diff.

Thanks,
Konrad
 
> Signed-off-by: Serguey Parkhomovsky <sergueyparkhomovsky@gmail.com>
> ---
> v2: Don't break the build, and fix the warnings by defining the functions in libcfs.h.
>  drivers/staging/lustre/include/linux/libcfs/libcfs.h | 3 +++
>  drivers/staging/lustre/lustre/libcfs/module.c        | 2 --
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/staging/lustre/include/linux/libcfs/libcfs.h b/drivers/staging/lustre/include/linux/libcfs/libcfs.h
> index a6b2f90..4410d7f 100644
> --- a/drivers/staging/lustre/include/linux/libcfs/libcfs.h
> +++ b/drivers/staging/lustre/include/linux/libcfs/libcfs.h
> @@ -85,6 +85,9 @@ static inline int __is_po2(unsigned long long val)
>  
>  #include <linux/list.h>
>  
> +int libcfs_arch_init(void);
> +void libcfs_arch_cleanup(void);
> +
>  /* libcfs tcpip */
>  int libcfs_ipif_query(char *name, int *up, __u32 *ip, __u32 *mask);
>  int libcfs_ipif_enumerate(char ***names);
> diff --git a/drivers/staging/lustre/lustre/libcfs/module.c b/drivers/staging/lustre/lustre/libcfs/module.c
> index 2c4fc74..31a4d19 100644
> --- a/drivers/staging/lustre/lustre/libcfs/module.c
> +++ b/drivers/staging/lustre/lustre/libcfs/module.c
> @@ -334,8 +334,6 @@ extern struct mutex cfs_trace_thread_mutex;
>  extern struct cfs_wi_sched *cfs_sched_rehash;
>  
>  extern void libcfs_init_nidstrings(void);
> -extern int libcfs_arch_init(void);
> -extern void libcfs_arch_cleanup(void);
>  
>  static int init_libcfs_module(void)
>  {
> -- 
> 1.9.3
> 
> _______________________________________________
> devel mailing list
> devel@linuxdriverproject.org
> http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel

  reply	other threads:[~2014-12-31 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-31  8:48 [PATCH v2] staging: lustre: linux-prim.c: fix sparse warnings about static declaration Serguey Parkhomovsky
2014-12-31 10:40 ` Konrad Zapalowicz [this message]
2014-12-31 18:55   ` Serguey Parkhomovsky

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=20141231104029.GA25819@t400 \
    --to=bergo.torino@gmail.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=sergueyparkhomovsky@gmail.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