On Mon, Dec 13, 2021 at 07:39:27PM +0100, Toke Høiland-Jørgensen wrote: > Jakub Kicinski <kuba@xxxxxxxxxx> writes: > > > On Mon, 13 Dec 2021 16:48:37 +0100 Toke Høiland-Jørgensen wrote: > >> > Status notification when checks are failing? Hopefully not, we don't > >> > want people posting patches just to get them tested... > >> > >> Well no, but sometimes a patch will have failures despite the best > >> efforts of the submitter (otherwise what's the point of the checks?). > >> Right now the only way for me to discover that there's an issue is to go > >> look at the patchwork web interface, and I wanted something that better > >> suits my workflow (i.e., that's not in a web browser). > > > > I think that the maintainer should notify the submitter about > > the reason the patch state was changed (with the exception of > > patches for a different tree, maybe). I know Kees has been > > trying to add more meaningful states to patchwork but I can > > never guess the meaning of those either :S So no automated > > state checker can replace the maintainer's reply. > > Well, sometimes the maintainers forget to reply entirely :) > > And yeah, I do realise that no bot is going to be able to tell me > exactly what the current status is, I just want a tool to help me > manually keep track... I've mostly been trying to capture the state of the patch review conversation with some kind of flag in patchwork. For KSPP, we've documented it here: https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project/Patch_Tracking -- Kees Cook
