From: Andrew Lunn <andrew@lunn.ch>
To: netdev <netdev@vger.kernel.org>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
linux-kbuild@vger.kernel.org, clang-built-linux@googlegroups.com,
Andrew Lunn <andrew@lunn.ch>
Subject: [PATCH RFC/RFT 0/2] W=1 by default for Ethernet PHY subsystem
Date: Sat, 19 Sep 2020 21:02:56 +0200 [thread overview]
Message-ID: <20200919190258.3673246-1-andrew@lunn.ch> (raw)
There is a movement to make the code base compile clean with W=1. Some
subsystems are already clean. In order to keep them clean, we need
developers to build new code with W=1 by default in these subsystems.
This patchset refactors the core Makefile warning code to allow the
additional warnings W=1 adds available to any Makefile. The Ethernet
PHY subsystem Makefiles then make use of this to make W=1 the default
for this subsystem.
RFT since i've only tested with x86 and arm with a modern gcc. Is the
code really clean for older compilers? For clang?
Andrew Lunn (2):
scripts: Makefile.extrawarn: Add W=1 warnings to a symbol
net: phylib: Enable W=1 by default
drivers/net/mdio/Makefile | 3 +++
drivers/net/pcs/Makefile | 3 +++
drivers/net/phy/Makefile | 3 +++
scripts/Makefile.extrawarn | 33 ++++++++++++++++++---------------
4 files changed, 27 insertions(+), 15 deletions(-)
--
2.28.0
next reply other threads:[~2020-09-19 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 19:02 Andrew Lunn [this message]
2020-09-19 19:02 ` [PATCH RFC/RFT 1/2] scripts: Makefile.extrawarn: Add W=1 warnings to a symbol Andrew Lunn
2020-09-19 19:02 ` [PATCH RFC/RFT 2/2] net: phylib: Enable W=1 by default Andrew Lunn
2020-09-20 3:42 ` [PATCH RFC/RFT 0/2] W=1 by default for Ethernet PHY subsystem Masahiro Yamada
2020-09-20 14:53 ` Andrew Lunn
2021-02-10 18:39 ` Jason Gunthorpe
2021-02-10 18:43 ` Jakub Kicinski
2021-02-10 18:55 ` Jason Gunthorpe
2021-02-10 19:01 ` Andrew Lunn
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=20200919190258.3673246-1-andrew@lunn.ch \
--to=andrew@lunn.ch \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox