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] [day] [month] [year] [list]

Date:   Thu, 18 Feb 2021 09:31:08 +0000
From:   Lee Jones <lee.jones@...aro.org>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     Andrew Lunn <andrew@...n.ch>, Stephen Boyd <sboyd@...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 Wed, 17 Feb 2021, Jakub Kicinski wrote:

> On Tue, 16 Feb 2021 08:20:46 +0000 Lee Jones wrote:
> > On Mon, 15 Feb 2021, Jakub Kicinski wrote:
> > > On Mon, 15 Feb 2021 08:49:52 +0000 Lee Jones wrote:  
> > > > Yes, please share.  
> > > 
> > > https://github.com/kuba-moo/nipa  
> > 
> > Thanks for this.
> > 
> > Oh, I see.  So you conduct tests locally, then post them up in a
> > section called 'Checks' using the provided API.  
> 
> For some definition of "locally" - NIPA runs on a rented VM.

Right.  Infrastructure that you control vs by Patchwork.

> > I assume that Patchwork does not alert the user when something has
> > gone awry?  Is this something Nipa does?
> 
> The way we run it on netdev is maintainer-centric, IOW we see 
> the failures in patchwork and complain to people manually.
> The netdev mailing list gets too many messages as is, if NIPA 
> responded with results automatically (which is not that hard
> technically) my concern is that people would be more likely to
> send untested patches to the mailing list and rely on the bot.

That makes sense.  Thank you for the explanation.

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