From: Wei Yongjun <weiyj.lk@gmail.com> To: mfasheh@suse.com, jlbec@evilplan.org Cc: yongjun_wei@trendmicro.com.cn, ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org Subject: [PATCH -next] ocfs2: fix sparse non static symbol warning Date: Fri, 22 Nov 2013 10:43:20 +0800 [thread overview] Message-ID: <CAPgLHd9uPqx0fY7DQp2gWESb-yUZraWh7tpdMW6ao2Bq=DwYCA@mail.gmail.com> (raw) From: Wei Yongjun <yongjun_wei@trendmicro.com.cn> Fixes the following sparse warning: fs/ocfs2/stack_user.c:930:32: warning: symbol 'ocfs2_ls_ops' was not declared. Should it be static? Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn> --- fs/ocfs2/stack_user.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ocfs2/stack_user.c b/fs/ocfs2/stack_user.c index eca3f93..9b18f4e 100644 --- a/fs/ocfs2/stack_user.c +++ b/fs/ocfs2/stack_user.c @@ -927,7 +927,7 @@ static void user_recover_done(void *arg, struct dlm_slot *slots, wake_up(&lc->oc_wait); } -const struct dlm_lockspace_ops ocfs2_ls_ops = { +static const struct dlm_lockspace_ops ocfs2_ls_ops = { .recover_prep = user_recover_prep, .recover_slot = user_recover_slot, .recover_done = user_recover_done,
WARNING: multiple messages have this Message-ID (diff)
From: Wei Yongjun <weiyj.lk@gmail.com> To: mfasheh@suse.com, jlbec@evilplan.org Cc: yongjun_wei@trendmicro.com.cn, ocfs2-devel@oss.oracle.com, linux-kernel@vger.kernel.org Subject: [Ocfs2-devel] [PATCH -next] ocfs2: fix sparse non static symbol warning Date: Fri, 22 Nov 2013 02:43:28 -0000 [thread overview] Message-ID: <CAPgLHd9uPqx0fY7DQp2gWESb-yUZraWh7tpdMW6ao2Bq=DwYCA@mail.gmail.com> (raw) From: Wei Yongjun <yongjun_wei@trendmicro.com.cn> Fixes the following sparse warning: fs/ocfs2/stack_user.c:930:32: warning: symbol 'ocfs2_ls_ops' was not declared. Should it be static? Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn> --- fs/ocfs2/stack_user.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/ocfs2/stack_user.c b/fs/ocfs2/stack_user.c index eca3f93..9b18f4e 100644 --- a/fs/ocfs2/stack_user.c +++ b/fs/ocfs2/stack_user.c @@ -927,7 +927,7 @@ static void user_recover_done(void *arg, struct dlm_slot *slots, wake_up(&lc->oc_wait); } -const struct dlm_lockspace_ops ocfs2_ls_ops = { +static const struct dlm_lockspace_ops ocfs2_ls_ops = { .recover_prep = user_recover_prep, .recover_slot = user_recover_slot, .recover_done = user_recover_done,
next reply other threads:[~2013-11-22 2:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-22 2:43 Wei Yongjun [this message] 2013-11-22 2:43 ` [Ocfs2-devel] [PATCH -next] ocfs2: fix sparse non static symbol warning Wei Yongjun
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='CAPgLHd9uPqx0fY7DQp2gWESb-yUZraWh7tpdMW6ao2Bq=DwYCA@mail.gmail.com' \ --to=weiyj.lk@gmail.com \ --cc=jlbec@evilplan.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mfasheh@suse.com \ --cc=ocfs2-devel@oss.oracle.com \ --cc=yongjun_wei@trendmicro.com.cn \ /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: linkBe 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.