[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK8P3a3ieV29jgh0jhioN3KjZCfP2drPAQme_+1oMuTTSiA4NQ@mail.gmail.com>
Date: Thu, 12 Jan 2017 23:42:30 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre Torgue <alexandre.torgue@...com>,
Gabriel Fernandez <gabriel.fernandez@...com>,
Rob Herring <robh@...nel.org>,
Christophe JAILLET <christophe.jaillet@...adoo.fr>,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] clk: stm32f4: avoid uninitialized variable access
On Thu, Jan 12, 2017 at 11:06 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
>
> Applied to clk-next. Seems I need to update my compiler to find
> these warnings.
I'm currently playing with gcc-7, which adds a lot of new warnings
(including many false positives). gcc-6 was supposed to have better
warnings than 5, but I didn't find the difference that noticeable. 5
or 6 is probably best at the moment, and if you have at least 4.9
there is no urgent need to upgrade.
Arnd
Powered by blists - more mailing lists