All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: outreachy-kernel@googlegroups.com
Cc: Shraddha Barke <shraddha.6596@gmail.com>
Subject: Re: [Outreachy kernel] [PATCH 0/6] Declare functions and structures as static
Date: Thu, 01 Oct 2015 22:17 +0200	[thread overview]
Message-ID: <1618733.OsocIDNLYM@wuerfel> (raw)
In-Reply-To: <1443720581-11352-1-git-send-email-shraddha.6596@gmail.com>

On Thursday 01 October 2015 22:59:35 Shraddha Barke wrote:
> These patches declare the functions and structures which are not
> used anywhere else as static.
> 
> 
> Shraddha Barke (6):
>   Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_merge as static
>   Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_free as static
>   Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_expand as static
>   Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_choose as static
>   Staging: lustre: ptlrpc: Declare sptlrpc_req_replace_dead_ctx as
>     static
>   Staging: lustre: ptlrpc: Declare sptlrpc_parse_rule as static
> 
> 

Individually, each of these looks good and can be applied

Reviewed-by: Arnd Bergmann <arnd@arndb.de>

Now that you get the principle right, I think it would be better
to continue with similar patches that do multiple functions at
once and look at the bigger picture. In case of this series, it would
be worth noting that there are two more sptlrpc_rule_set_* functions,
and neither of them should be global. The sptlrpc_rule_set_init()
one is slightly different because it's static inline but can simply
be moved into the file that holds the other functions.

Try to find patterns like this and then handle all symbols that
fall into a similar category as a combined patch.

	Arnd


      parent reply	other threads:[~2015-10-01 20:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 17:29 [PATCH 0/6] Declare functions and structures as static Shraddha Barke
2015-10-01 17:29 ` [PATCH 1/6] Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_merge " Shraddha Barke
2015-10-01 17:29 ` [PATCH 2/6] Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_free " Shraddha Barke
2015-10-01 17:29 ` [PATCH 3/6] Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_expand " Shraddha Barke
2015-10-01 17:29 ` [PATCH 4/6] Staging: lustre: ptlrpc: Declare sptlrpc_rule_set_choose " Shraddha Barke
2015-10-02  4:57   ` [Outreachy kernel] " Sudip Mukherjee
2015-10-02  5:38     ` Shraddha Barke
2015-10-02  5:47       ` Sudip Mukherjee
2015-10-02  5:56         ` Shraddha Barke
2015-10-02  6:31           ` Sudip Mukherjee
2015-10-01 17:29 ` [PATCH 5/6] Staging: lustre: ptlrpc: Declare sptlrpc_req_replace_dead_ctx " Shraddha Barke
2015-10-01 17:29 ` [PATCH 6/6] Staging: lustre: ptlrpc: Declare sptlrpc_parse_rule " Shraddha Barke
2015-10-01 20:17 ` Arnd Bergmann [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=1618733.OsocIDNLYM@wuerfel \
    --to=arnd@arndb.de \
    --cc=outreachy-kernel@googlegroups.com \
    --cc=shraddha.6596@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.