public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Boris Brezillon <boris.brezillon@free-electrons•com>
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 19:19:57 +1100	[thread overview]
Message-ID: <20161212191957.0d607489@canb.auug.org.au> (raw)
In-Reply-To: <20161212090521.0450504e@bbrezillon>

Hi Boris,

On Mon, 12 Dec 2016 09:05:21 +0100 Boris Brezillon <boris.brezillon@free-electrons•com> wrote:
>
> 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).

I use a powerpc-le hosted cross compiler gcc-5.2.0.

-- 
Cheers,
Stephen Rothwell

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

Thread overview: 17+ 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
2016-12-12  8:19   ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-09  1:27 Stephen Rothwell
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=20161212191957.0d607489@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=boris.brezillon@free-electrons$(echo .)com \
    --cc=eric@anholt$(echo .)net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mturquette@baylibre$(echo .)com \
    --cc=sboyd@codeaurora$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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