linux-kernel - Re: [PATCH 00/21] [Set 2] Rid W=1 warnings from Clock

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 15 Feb 2021 08:49:52 +0000
From:   Lee Jones <lee.jones@...aro.org>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Stephen Boyd <sboyd@...nel.org>, Jakub Kicinski <kuba@...nel.org>,
        Prashant Gaikwad <pgaikwad@...dia.com>,
        Tomer Maimon <tmaimon77@...il.com>,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Michael Turquette <mturquette@...libre.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rajeev Kumar <rajeev-dlh.kumar@...com>,
        Jan Kotas <jank@...ence.com>,
        Russell King <linux@...linux.org.uk>,
        Fabio Estevam <festevam@...il.com>, linux-clk@...r.kernel.org,
        Boris BREZILLON <boris.brezillon@...e-electrons.com>,
        Ahmad Fatoum <a.fatoum@...gutronix.de>,
        Benjamin Fair <benjaminfair@...gle.com>,
        Emilio López <emilio@...pez.com.ar>,
        Viresh Kumar <vireshk@...nel.org>, openbmc@...ts.ozlabs.org,
        Michal Simek <michal.simek@...inx.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Nancy Yuen <yuenn@...gle.com>, Chen-Yu Tsai <wens@...e.org>,
        Andy Gross <agross@...nel.org>, Loc Ho <lho@....com>,
        NXP Linux Team <linux-imx@....com>,
        Richard Woodruff <r-woodruff2@...com>,
        Tali Perry <tali.perry1@...il.com>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        linux-arm-msm@...r.kernel.org,
        Sascha Hauer <s.hauer@...gutronix.de>,
        Maxime Ripard <mripard@...nel.org>,
        linux-tegra@...r.kernel.org, linux-omap@...r.kernel.org,
        Shiraz Hashim <shiraz.linux.kernel@...il.com>,
        linux-arm-kernel@...ts.infradead.org,
        Sören Brinkmann <soren.brinkmann@...inx.com>,
        Jernej Skrabec <jernej.skrabec@...l.net>,
        Tero Kristo <kristo@...nel.org>,
        Rajan Vaja <rajan.vaja@...inx.com>,
        Avi Fishman <avifishman70@...il.com>,
        Patrick Venture <venture@...gle.com>,
        Peter De Schrijver <pdeschrijver@...dia.com>,
        linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
        Nuvoton Technologies <tali.perry@...oton.com>,
        Thierry Reding <thierry.reding@...il.com>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Shawn Guo <shawnguo@...nel.org>
Subject: Re: [PATCH 00/21] [Set 2] Rid W=1 warnings from Clock

On Sun, 14 Feb 2021, Andrew Lunn wrote:

> On Sun, Feb 14, 2021 at 01:00:42PM -0800, Stephen Boyd wrote:
> > Quoting Andrew Lunn (2021-02-13 08:04:34)
> > > > 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.
> > > 
> > 
> > Yes the kernel.org patchwork instance is used but I don't see any bot
> > putting test results there. How is that done?
> > 
> > https://patchwork.kernel.org/project/linux-clk/list/
> 
> Compare this with for example:
> 
> https://patchwork.kernel.org/project/netdevbpf/patch/20210213175257.28642-1-ap420073@gmail.com/

Oh, that's nice.

> Jakub can explain how he added these checks.

Yes, please share.

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog