From: tip-bot for YueHaibing <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: ferdinand.blomqvist@gmail.com, yuehaibing@huawei.com,
linux-kernel@vger.kernel.org, tglx@linutronix.de, hpa@zytor.com,
hulkci@huawei.com, mingo@kernel.org
Subject: [tip:core/rslib] rslib: Make some functions static
Date: Mon, 1 Jul 2019 23:46:24 -0700 [thread overview]
Message-ID: <tip-ede7c247abfaeef62484cfff320b072ec2b1dca0@git.kernel.org> (raw)
In-Reply-To: <20190702061847.26060-1-yuehaibing@huawei.com>
Commit-ID: ede7c247abfaeef62484cfff320b072ec2b1dca0
Gitweb: https://git.kernel.org/tip/ede7c247abfaeef62484cfff320b072ec2b1dca0
Author: YueHaibing <yuehaibing@huawei.com>
AuthorDate: Tue, 2 Jul 2019 14:18:47 +0800
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 2 Jul 2019 08:41:37 +0200
rslib: Make some functions static
Fix sparse warnings:
lib/reed_solomon/test_rslib.c:313:5: warning: symbol 'ex_rs_helper' was not declared. Should it be static?
lib/reed_solomon/test_rslib.c:349:5: warning: symbol 'exercise_rs' was not declared. Should it be static?
lib/reed_solomon/test_rslib.c:407:5: warning: symbol 'exercise_rs_bc' was not declared. Should it be static?
Reported-by: Hulk Robot <hulkci@huawei.com>
Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: <ferdinand.blomqvist@gmail.com>
Link: https://lkml.kernel.org/r/20190702061847.26060-1-yuehaibing@huawei.com
---
lib/reed_solomon/test_rslib.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/lib/reed_solomon/test_rslib.c b/lib/reed_solomon/test_rslib.c
index eb62e0393c80..4eb29f365ece 100644
--- a/lib/reed_solomon/test_rslib.c
+++ b/lib/reed_solomon/test_rslib.c
@@ -310,8 +310,8 @@ static void test_uc(struct rs_control *rs, int len, int errs,
stat->nwords += trials;
}
-int ex_rs_helper(struct rs_control *rs, struct wspace *ws,
- int len, int trials, int method)
+static int ex_rs_helper(struct rs_control *rs, struct wspace *ws,
+ int len, int trials, int method)
{
static const char * const desc[] = {
"Testing correction buffer interface...",
@@ -346,8 +346,8 @@ int ex_rs_helper(struct rs_control *rs, struct wspace *ws,
return retval;
}
-int exercise_rs(struct rs_control *rs, struct wspace *ws,
- int len, int trials)
+static int exercise_rs(struct rs_control *rs, struct wspace *ws,
+ int len, int trials)
{
int retval = 0;
@@ -404,8 +404,8 @@ static void test_bc(struct rs_control *rs, int len, int errs,
stat->nwords += trials;
}
-int exercise_rs_bc(struct rs_control *rs, struct wspace *ws,
- int len, int trials)
+static int exercise_rs_bc(struct rs_control *rs, struct wspace *ws,
+ int len, int trials)
{
struct bcstat stat = {0, 0, 0, 0};
int nroots = rs->codec->nroots;
prev parent reply other threads:[~2019-07-02 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 6:18 [PATCH -next] rslib: Make some functions static YueHaibing
2019-07-02 6:46 ` tip-bot for YueHaibing [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=tip-ede7c247abfaeef62484cfff320b072ec2b1dca0@git.kernel.org \
--to=tipbot@zytor.com \
--cc=ferdinand.blomqvist@gmail.com \
--cc=hpa@zytor.com \
--cc=hulkci@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=yuehaibing@huawei.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