All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nickolaus Woodruff <nickolauswoodruff@gmail.com>
To: olegdrokin@intel.com, andreasdilger@intel.com,
	gregkh@linuxfoundation.org
Cc: HPDD-discuss@ml01.01.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] staging: lustre: Make cfs_sched_rehash static
Date: Mon, 6 Apr 2015 22:02:27 -0400	[thread overview]
Message-ID: <20150407020227.GA1500@Caladan> (raw)

This patch fixes the following sparse warning:

CHECK   drivers/staging/lustre/lustre/libcfs/hash.c
drivers/staging/lustre/lustre/libcfs/hash.c:119:21: warning: symbol
'cfs_sched_rehash' was not declared. Should it be static?

Signed-off-by: Nickolaus Woodruff <nickolauswoodruff@gmail.com>
---
 drivers/staging/lustre/lustre/libcfs/hash.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/lustre/lustre/libcfs/hash.c b/drivers/staging/lustre/lustre/libcfs/hash.c
index a55567e..a4920a2 100644
--- a/drivers/staging/lustre/lustre/libcfs/hash.c
+++ b/drivers/staging/lustre/lustre/libcfs/hash.c
@@ -116,7 +116,7 @@ module_param(warn_on_depth, uint, 0644);
 MODULE_PARM_DESC(warn_on_depth, "warning when hash depth is high.");
 #endif

-struct cfs_wi_sched *cfs_sched_rehash;
+static struct cfs_wi_sched *cfs_sched_rehash;

 static inline void
 cfs_hash_nl_lock(union cfs_hash_lock *lock, int exclusive) {}
--
1.9.1


             reply	other threads:[~2015-04-07  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  2:02 Nickolaus Woodruff [this message]
2015-04-07  9:42 ` [PATCH] staging: lustre: Make cfs_sched_rehash static Sudip Mukherjee
2015-04-07 16:01 ` [HPDD-discuss] " Drokin, Oleg

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=20150407020227.GA1500@Caladan \
    --to=nickolauswoodruff@gmail.com \
    --cc=HPDD-discuss@ml01.01.org \
    --cc=andreasdilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olegdrokin@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 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.