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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 13 Feb 2021 17:04:34 +0100
From:   Andrew Lunn <>
To:     Stephen Boyd <>
Cc:     Lee Jones <>,
        Prashant Gaikwad <>,
        Tomer Maimon <>,
        Geert Uytterhoeven <>,
        Michael Turquette <>,
        Bjorn Andersson <>,
        Rajeev Kumar <>,
        Jan Kotas <>,
        Russell King <>,
        Fabio Estevam <>,,
        Boris BREZILLON <>,
        Ahmad Fatoum <>,
        Benjamin Fair <>,
        Emilio López <>,
        Viresh Kumar <>,,
        Michal Simek <>,
        Jonathan Hunter <>,
        Nancy Yuen <>, Chen-Yu Tsai <>,
        Andy Gross <>, Loc Ho <>,
        NXP Linux Team <>,
        Richard Woodruff <>,
        Tali Perry <>,
        Philipp Zabel <>,,
        Sascha Hauer <>,
        Maxime Ripard <>,,,
        Shiraz Hashim <>,,
        Sören Brinkmann <>,
        Jernej Skrabec <>,
        Tero Kristo <>,
        Rajan Vaja <>,
        Avi Fishman <>,
        Patrick Venture <>,
        Peter De Schrijver <>,,,
        Nuvoton Technologies <>,
        Thierry Reding <>,
        Pengutronix Kernel Team <>,
        Shawn Guo <>
Subject: Re: [PATCH 00/21] [Set 2] Rid W=1 warnings from Clock

> I'm trying to see if we can make lives better for everyone by exposing
> the warnings by default in the drivers/clk/ directory now that there are
> supposedly none left. Shouldn't we tighten the screws now that we've
> cleaned them?

Do you use patchwork? netdev has a bot attached which applies the
patch and does a W=1 build, and will report any new warnings. But it
does not email the developer, as far as i know. It is up to you as the
maintainer to reject the patch and say why.


Powered by blists - more mailing lists