[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210210183917.GA1471624@nvidia.com>
Date: Wed, 10 Feb 2021 14:39:17 -0400
From: Jason Gunthorpe <jgg@...dia.com>
To: Andrew Lunn <andrew@...n.ch>, Nathan Chancellor <nathan@...nel.org>
CC: Masahiro Yamada <masahiroy@...nel.org>,
netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
"Michal Marek" <michal.lkml@...kovi.net>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: [PATCH RFC/RFT 0/2] W=1 by default for Ethernet PHY subsystem
On Sun, Sep 20, 2020 at 04:53:51PM +0200, Andrew Lunn wrote:
> How often are new W=1 flags added? My patch exported
> KBUILD_CFLAGS_WARN1. How about instead we export
> KBUILD_CFLAGS_WARN1_20200920. A subsystem can then sign up to being
> W=1 clean as for the 20200920 definition of W=1.
I think this is a reasonable idea.
I'm hitting exactly the issue this series is trying to solve, Lee
invested a lot of effort to make drivers/infiniband/ W=1 clean, but
as maintainer I can't sustain this since there is no easy way to have
a warning free compile and get all extra warnings. Also all my
submitters are not running with W=1
I need kbuild to get everyone on the same page to be able to sustain
the warning clean up. We've already had a regression and it has only
been a few weeks :(
Andrew, would you consider respinning this series in the above form?
Thanks,
Jason
Powered by blists - more mailing lists