mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@lip6.fr>
To: "Zoltán Lajos Kis" <zoltan.lajos.kis@gmail.com>
Cc: oleg.drokin@intel.com, andreas.dilger@intel.com,
	gregkh@linuxfoundation.org, bgolaszewski@baylibre.com,
	john.hammond@intel.com, dmitry4ever@gmail.com,
	HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: lustre: ptlrpc service.c fix sparse static warnings
Date: Sun, 2 Aug 2015 22:07:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1508022205070.2044@localhost6.localdomain6> (raw)
In-Reply-To: <1438545085-23103-1-git-send-email-zoltan.lajos.kis@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2824 bytes --]

On Sun, 2 Aug 2015, Zoltán Lajos Kis wrote:

> Fixes the following sparse warnings:
> 
> drivers/staging/lustre/lustre/ptlrpc/service.c:72:35: warning: symbol
> 'ptlrpc_alloc_rqbd' was not declared. Should it be static?
> 1065 drivers/staging/lustre/lustre/ptlrpc/service.c:105:1: warning:
> symbol 'ptlrpc_free_rqbd' was not declared. Should it be static?
> 1066 drivers/staging/lustre/lustre/ptlrpc/service.c:122:1: warning:
> symbol 'ptlrpc_grow_req_bufs' was not declared. Should it be static?
> 1067 drivers/staging/lustre/lustre/ptlrpc/service.c:3055:5: warning:
> symbol 'ptlrpc_svcpt_health_check' was not declared. Should it be
> static?

Try to come up with a commit message that says something more than "fix".  
Something like "Make static some functions that are not used outside the 
file in which they are defined" would make clear what is done and why.  It 
would be nice to say that sparse helped you find the problem, but goal 
of the change should not be to silence sparse.

julia

> Signed-off-by: Zoltán Lajos Kis <zoltan.lajos.kis@gmail.com>"
> ---
>  drivers/staging/lustre/lustre/ptlrpc/service.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/staging/lustre/lustre/ptlrpc/service.c b/drivers/staging/lustre/lustre/ptlrpc/service.c
> index cf9477d..d3265a8 100644
> --- a/drivers/staging/lustre/lustre/ptlrpc/service.c
> +++ b/drivers/staging/lustre/lustre/ptlrpc/service.c
> @@ -69,7 +69,7 @@ LIST_HEAD(ptlrpc_all_services);
>  /** Used to protect the \e ptlrpc_all_services list */
>  struct mutex ptlrpc_all_services_mutex;
>  
> -struct ptlrpc_request_buffer_desc *
> +static struct ptlrpc_request_buffer_desc *
>  ptlrpc_alloc_rqbd(struct ptlrpc_service_part *svcpt)
>  {
>  	struct ptlrpc_service *svc = svcpt->scp_service;
> @@ -101,7 +101,7 @@ ptlrpc_alloc_rqbd(struct ptlrpc_service_part *svcpt)
>  	return rqbd;
>  }
>  
> -void
> +static void
>  ptlrpc_free_rqbd(struct ptlrpc_request_buffer_desc *rqbd)
>  {
>  	struct ptlrpc_service_part *svcpt = rqbd->rqbd_svcpt;
> @@ -118,7 +118,7 @@ ptlrpc_free_rqbd(struct ptlrpc_request_buffer_desc *rqbd)
>  	kfree(rqbd);
>  }
>  
> -int
> +static int
>  ptlrpc_grow_req_bufs(struct ptlrpc_service_part *svcpt, int post)
>  {
>  	struct ptlrpc_service *svc = svcpt->scp_service;
> @@ -3052,7 +3052,7 @@ EXPORT_SYMBOL(ptlrpc_unregister_service);
>   * Right now, it just checks to make sure that requests aren't languishing
>   * in the queue.  We'll use this health check to govern whether a node needs
>   * to be shot, so it's intentionally non-aggressive. */
> -int ptlrpc_svcpt_health_check(struct ptlrpc_service_part *svcpt)
> +static int ptlrpc_svcpt_health_check(struct ptlrpc_service_part *svcpt)
>  {
>  	struct ptlrpc_request *request = NULL;
>  	struct timeval right_now;
> -- 
> 1.9.1
> 
> 

      reply	other threads:[~2015-08-02 20:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02 19:51 Zoltán Lajos Kis
2015-08-02 20:07 ` Julia Lawall [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=alpine.DEB.2.02.1508022205070.2044@localhost6.localdomain6 \
    --to=julia.lawall@lip6.fr \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=andreas.dilger@intel.com \
    --cc=bgolaszewski@baylibre.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry4ever@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=john.hammond@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg.drokin@intel.com \
    --cc=zoltan.lajos.kis@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

all inboxes | Powered by JetHome®