From: Ryan Swan <ryan@ryanswan.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH] staging: lov.ko: lov_object.c: fix sparse warning setting function to static
Date: Mon, 17 Oct 2016 19:22:01 -0000 [thread overview]
Message-ID: <1476732112-21234-1-git-send-email-ryan@ryanswan.com> (raw)
Fixed: sparse WARNING: symbol 'lov_read_and_clear_async_rc' was not declared. Should it be static?
Signed-off-by: Ryan Swan <ryan@ryanswan.com>
---
drivers/staging/lustre/lustre/lov/lov_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lov/lov_object.c b/drivers/staging/lustre/lustre/lov/lov_object.c
index 82b99e0..c42eef6 100644
--- a/drivers/staging/lustre/lustre/lov/lov_object.c
+++ b/drivers/staging/lustre/lustre/lov/lov_object.c
@@ -1532,7 +1532,7 @@ struct lov_stripe_md *lov_lsm_addref(struct lov_object *lov)
return lsm;
}
-int lov_read_and_clear_async_rc(struct cl_object *clob)
+static int lov_read_and_clear_async_rc(struct cl_object *clob)
{
struct lu_object *luobj;
int rc = 0;
--
2.7.4
next reply other threads:[~2016-10-17 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 19:22 Ryan Swan [this message]
2016-10-17 19:38 ` [lustre-devel] [PATCH] staging: lov.ko: lov_object.c: fix sparse warning setting function to static Greg KH
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=1476732112-21234-1-git-send-email-ryan@ryanswan.com \
--to=ryan@ryanswan.com \
--cc=lustre-devel@lists.lustre.org \
/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.