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@xxxxxxxxx/ 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
