From: Stephen Boyd <sboyd@kernel.org>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Subject: Re: linux-next: build warning after merge of the clk tree
Date: Fri, 16 Aug 2019 11:10:48 -0700 [thread overview]
Message-ID: <20190816181049.630BE206C1@mail.kernel.org> (raw)
In-Reply-To: <20190816095732.0ffea609@canb.auug.org.au>
Quoting Stephen Rothwell (2019-08-15 16:57:32)
> Hi all,
>
> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
> produced this warning:
>
> drivers/clk/actions/owl-common.c: In function 'owl_clk_probe':
> drivers/clk/actions/owl-common.c:71:24: warning: 'hw' may be used uninitialized in this function [-Wmaybe-uninitialized]
> const char *name = hw->init->name;
> ~~^~~~~~
>
> Introduced by commit
>
> 20cac6d02815 ("clk: actions: Don't reference clk_init_data after registration")
>
> Clearly not a false positive. :-(
>
Thanks. I fixed it now.
next prev parent reply other threads:[~2019-08-16 18:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 23:57 linux-next: build warning after merge of the clk tree Stephen Rothwell
2019-08-16 18:10 ` Stephen Boyd [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-29 23:53 Stephen Rothwell
2020-06-30 8:11 ` Maxime Ripard
2020-07-08 11:10 ` Stephen Rothwell
2020-07-16 0:25 ` Stephen Boyd
2019-04-30 0:19 Stephen Rothwell
2019-04-30 1:44 ` Anson Huang
2019-04-30 5:56 ` Stephen Rothwell
2018-10-17 21:51 Stephen Rothwell
2018-10-18 18:21 ` Stephen Boyd
2016-12-11 21:39 Stephen Rothwell
2016-12-12 8:05 ` Boris Brezillon
2016-12-12 8:19 ` Stephen Rothwell
2015-05-06 4:05 Stephen Rothwell
2015-05-06 4:41 ` Stephen Boyd
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=20190816181049.630BE206C1@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mturquette@baylibre.com \
--cc=sfr@canb.auug.org.au \
/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).