[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e669408a-727d-c1f8-cb91-05e950ec2881@roeck-us.net>
Date: Fri, 3 Jun 2022 08:51:48 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: "Hawkins, Nick" <nick.hawkins@....com>,
Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,
"Verdun, Jean-Marie" <verdun@....com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>,
"linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>
Subject: Re: mainline build failure due to 6b47441bed49 ("watchdog: hpe-wdt:
Introduce HPE GXP Watchdog")
On 6/3/22 08:29, Hawkins, Nick wrote:
>> I sent a patch fixing the problem a minute ago.
>
> Thank you for correcting this. I had the compiler set to W=1, is there another option I should be using to catch errors like this?
>
arm:allmodconfig reproduces the problem. I had seen it as well,
which is why I sent a fix. The key is to enable -Werror
(CONFIG_WERROR=y), not W=1.
Guenter
Powered by blists - more mailing lists