From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: linux-next: build warnings after merge of the pinctrl tree
Date: Wed, 16 Nov 2016 10:11:33 +1100 [thread overview]
Message-ID: <20161116101133.6ad1d974@canb.auug.org.au> (raw)
Hi Linus,
After merging the pinctrl tree, today's linux-next build
(arm_multi_v7_defconfig) produced these warnings:
drivers/pinctrl/sunxi/pinctrl-sunxi.c: In function 'sunxi_pinctrl_init':
drivers/pinctrl/sunxi/pinctrl-sunxi.c:1191:8: warning: 'best_div' may be used uninitialized in this function [-Wmaybe-uninitialized]
div = hosc_div;
^
drivers/pinctrl/sunxi/pinctrl-sunxi.c:1128:31: note: 'best_div' was declared here
unsigned int best_diff = ~0, best_div;
^
drivers/pinctrl/sunxi/pinctrl-sunxi.c:1194:8: warning: 'best_div' may be used uninitialized in this function [-Wmaybe-uninitialized]
div = losc_div;
^
drivers/pinctrl/sunxi/pinctrl-sunxi.c:1128:31: note: 'best_div' was declared here
unsigned int best_diff = ~0, best_div;
^
Introduced by commit
7c926492d38a ("pinctrl: sunxi: Add support for interrupt debouncing")
--
Cheers,
Stephen Rothwell
reply other threads:[~2016-11-15 23:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20161116101133.6ad1d974@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maxime.ripard@free-electrons.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;
as well as URLs for NNTP newsgroup(s).