From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Gregory CLEMENT <gregory.clement@free-electrons.com>
Subject: linux-next: build warning after merge of the rtc tree
Date: Tue, 10 Jan 2017 14:01:00 +1100 [thread overview]
Message-ID: <20170110140100.4a5a0158@canb.auug.org.au> (raw)
Hi Alexandre,
After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
produced this warning:
drivers/rtc/rtc-armada38x.c: In function 'read_rtc_register_wa':
drivers/rtc/rtc-armada38x.c:131:25: warning: 'index_max' may be used uninitialized in this function [-Wmaybe-uninitialized]
return rtc->val_to_freq[index_max].value;
^
Introduced by commit
61cffa2438e3 ("rtc: armada38x: Follow the new recommendation for errata implementation")
--
Cheers,
Stephen Rothwell
next reply other threads:[~2017-01-10 3:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 3:01 Stephen Rothwell [this message]
2017-01-10 10:59 ` linux-next: build warning after merge of the rtc tree Alexandre Belloni
-- strict thread matches above, loose matches on Subject: below --
2020-03-23 5:24 Stephen Rothwell
2020-03-17 5:30 Stephen Rothwell
2019-10-30 4:41 Stephen Rothwell
2019-11-08 5:29 ` Stephen Rothwell
2019-11-08 15:20 ` Alexandre Belloni
2019-08-21 6:31 Stephen Rothwell
2019-03-28 1:23 Stephen Rothwell
2019-03-28 1:36 ` Joel Stanley
2019-03-28 1:57 ` Alexandre Belloni
2019-03-28 2:09 ` Joel Stanley
2018-03-21 6:44 Stephen Rothwell
2017-07-06 4:24 Stephen Rothwell
2017-07-06 5:54 ` Heiner Kallweit
2017-07-06 6:59 ` Alexandre Belloni
2017-06-29 5:42 Stephen Rothwell
2017-01-13 3:18 Stephen Rothwell
2017-01-13 8:42 ` Amelie DELAUNAY
2016-07-11 8:12 Stephen Rothwell
2016-07-11 8:23 ` Uwe Kleine-König
2016-07-11 21:23 ` Alexandre Belloni
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=20170110140100.4a5a0158@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexandre.belloni@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).