All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Mike Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Anholt <eric@anholt.net>
Subject: Re: linux-next: build warning after merge of the clk tree
Date: Mon, 12 Dec 2016 09:05:21 +0100	[thread overview]
Message-ID: <20161212090521.0450504e@bbrezillon> (raw)
In-Reply-To: <20161212083944.5b6f2b54@canb.auug.org.au>

+Eric

Hi Stephen,

On Mon, 12 Dec 2016 08:39:44 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Hi all,
> 
> After merging the clk tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
> 
> drivers/clk/bcm/clk-bcm2835.c: In function 'bcm2835_clock_determine_rate':
> drivers/clk/bcm/clk-bcm2835.c:1069:18: warning: 'best_rate' may be used uninitialized in this function [-Wmaybe-uninitialized]
>   *prate = curdiv * best_rate;
>                   ^
> drivers/clk/bcm/clk-bcm2835.c:1032:16: note: 'best_rate' was declared here
>   unsigned long best_rate;
>                 ^
> 
> Introduced by commit
> 
>   155e8b3b0ee3 ("clk: bcm: Support rate change propagation on bcm2835 clocks")
> 

Thanks for the report (I just sent a patch fixing this warning).
May I ask which toolchain you're using, because my gcc failed to detect
this uninitialized variable (and this is not the first time I have this
problem).

Regards,

Boris

  reply	other threads:[~2016-12-12  8:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11 21:39 linux-next: build warning after merge of the clk tree Stephen Rothwell
2016-12-12  8:05 ` Boris Brezillon [this message]
2016-12-12  8:19   ` Stephen Rothwell
  -- 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-08-15 23:57 Stephen Rothwell
2019-08-16 18:10 ` 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
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=20161212090521.0450504e@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=eric@anholt.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.