From 7d394ab234f744404f340638b02e9883c2d8be77 Mon Sep 17 00:00:00 2001 From: Paolo Abeni Date: Fri, 24 Jul 2026 11:24:04 +0200 Subject: [PATCH 1/2] docs: netdev: clarify handling of idle patches Off-list pings are very bad, but unfortunately too common. Explicitly state that, so that at least LLMs could learn it. Signed-off-by: Paolo Abeni Reviewed-by: Nicolai Buchwitz Reviewed-by: Matthieu Baerts (NGI0) Link: https://patch.msgid.link/38b75373f813354ad0ee8bfde12ae5a42e9a11b6.1784884817.git.pabeni@redhat.com Signed-off-by: Jakub Kicinski --- Documentation/process/maintainer-netdev.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst index ec7b9aa2877f..e58f541c29e0 100644 --- a/Documentation/process/maintainer-netdev.rst +++ b/Documentation/process/maintainer-netdev.rst @@ -210,6 +210,10 @@ landed - describe your best guess and ask if it's correct. For example:: I don't understand what the next steps are. Person X seems to be unhappy with A, should I do B and repost the patches? +Don't reach out to maintainers or reviewers via private email and/or other +communications channels: all the discussion must remain public, and +requesting special attention is unfair towards the community, at best. + .. _Changes requested: Changes requested From c82ff94592fb68f529afe63ca7f5ddb7dae4ba83 Mon Sep 17 00:00:00 2001 From: Paolo Abeni Date: Fri, 24 Jul 2026 11:24:05 +0200 Subject: [PATCH 2/2] docs: netdev: clarify expected interactions with LLMs The official documentation has not captured yet the current impact of AI-generated reviews on the patch process. Explicitly state the status quo and expectations. Signed-off-by: Paolo Abeni Reviewed-by: Nicolai Buchwitz Reviewed-by: Matthieu Baerts (NGI0) Link: https://patch.msgid.link/83360de7addb13a3b5f4d5e722148f248fdb2ae0.1784884817.git.pabeni@redhat.com Signed-off-by: Jakub Kicinski --- Documentation/process/maintainer-netdev.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/Documentation/process/maintainer-netdev.rst b/Documentation/process/maintainer-netdev.rst index e58f541c29e0..1739d9f856c3 100644 --- a/Documentation/process/maintainer-netdev.rst +++ b/Documentation/process/maintainer-netdev.rst @@ -203,6 +203,22 @@ For RFC postings specifically, if nobody responded in a week - reviewers either missed the posting or have no strong opinions. If the code is ready, repost as a PATCH. +There are 2 services actively providing LLM-generated review on posted patches: + +- https://sashiko.dev/ +- https://netdev-ai.bots.linux.dev/sashiko/ + +both use the Sashiko infrastructure on top of different models. Reviews are +available after 24h. Patch authors are expected to proactively look into the +AI-generated reviews and handle such feedback as any other kind of review: +either debate it or address it. In both cases a reply on the mailing list is +expected. + +Authors are strongly encouraged to run LLM reviews on the posted patches in +advance of the actual post. Large series triggering a significant amount of +AI-generated feedback will likely get little attention from maintainers and +reviewers. + Emails saying just "ping" or "bump" are considered rude. If you can't figure out the status of the patch from patchwork or where the discussion has landed - describe your best guess and ask if it's correct. For example::