lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 19 Sep 2020 21:02:56 +0200 From: Andrew Lunn <andrew@...n.ch> To: netdev <netdev@...r.kernel.org> Cc: David Miller <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, Masahiro Yamada <masahiroy@...nel.org>, Michal Marek <michal.lkml@...kovi.net>, linux-kbuild@...r.kernel.org, clang-built-linux@...glegroups.com, Andrew Lunn <andrew@...n.ch> Subject: [PATCH RFC/RFT 0/2] W=1 by default for Ethernet PHY subsystem 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
Powered by blists - more mailing lists