From: Alexander Shiyan <shc_work@mail.ru>
To: barebox@lists.infradead.org
Subject: [PATCH 3/8] drivers/clk/clk-fixed-factor.c: Fix sparse warning
Date: Sun, 16 Feb 2014 11:24:32 +0400 [thread overview]
Message-ID: <1392535477-21275-3-git-send-email-shc_work@mail.ru> (raw)
In-Reply-To: <1392535477-21275-1-git-send-email-shc_work@mail.ru>
drivers/clk/clk-fixed-factor.c:38:16: warning: symbol 'clk_fixed_factor_ops' was not declared. Should it be static?
Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
---
drivers/clk/clk-fixed-factor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-fixed-factor.c b/drivers/clk/clk-fixed-factor.c
index 52e7c16..f0ecbd3 100644
--- a/drivers/clk/clk-fixed-factor.c
+++ b/drivers/clk/clk-fixed-factor.c
@@ -35,7 +35,7 @@ static unsigned long clk_fixed_factor_recalc_rate(struct clk *clk,
return (parent_rate / f->div) * f->mult;
}
-struct clk_ops clk_fixed_factor_ops = {
+static struct clk_ops clk_fixed_factor_ops = {
.recalc_rate = clk_fixed_factor_recalc_rate,
};
--
1.8.3.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-02-16 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 7:24 [PATCH 1/8] common/kallsyms.c: " Alexander Shiyan
2014-02-16 7:24 ` [PATCH 2/8] drivers/clk/clk-fixed.c: " Alexander Shiyan
2014-02-16 7:24 ` Alexander Shiyan [this message]
2014-02-16 7:24 ` [PATCH 4/8] drivers/clk/clk-mux.c: " Alexander Shiyan
2014-02-16 7:24 ` [PATCH 5/8] drivers/clk/clk-gate.c: " Alexander Shiyan
2014-02-16 7:24 ` [PATCH 6/8] drivers/clk/clk-divider-table.c: " Alexander Shiyan
2014-02-16 7:24 ` [PATCH 7/8] drivers/i2c/i2c.c: Fix sparse warnings Alexander Shiyan
2014-02-16 7:24 ` [PATCH 8/8] drivers/of/base.c: " Alexander Shiyan
2014-02-17 7:25 ` [PATCH 1/8] common/kallsyms.c: Fix sparse warning Sascha Hauer
2014-02-17 7:30 ` Alexander Shiyan
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=1392535477-21275-3-git-send-email-shc_work@mail.ru \
--to=shc_work@mail.ru \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox