All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolai Buchwitz <nb@tipi-net.de>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH net-next 1/2] docs: netdev: clarify handling of idle patches
Date: Fri, 24 Jul 2026 12:22:47 +0200	[thread overview]
Message-ID: <d9f57f7676bb223438298cf349359f49@tipi-net.de> (raw)
In-Reply-To: <38b75373f813354ad0ee8bfde12ae5a42e9a11b6.1784884817.git.pabeni@redhat.com>

On 24.7.2026 11:24, Paolo Abeni wrote:
> 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 <pabeni@redhat.com>
> ---
>  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

Reviewed-by: Nicolai Buchwitz <nb@tipi-net.de>

Thanks
Nicolai

  reply	other threads:[~2026-07-24 10:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  9:24 [PATCH net-next 0/2] docs: netdev: a couple of updates Paolo Abeni
2026-07-24  9:24 ` [PATCH net-next 1/2] docs: netdev: clarify handling of idle patches Paolo Abeni
2026-07-24 10:22   ` Nicolai Buchwitz [this message]
2026-07-24 13:35   ` Matthieu Baerts
2026-07-24  9:24 ` [PATCH net-next 2/2] docs: netdev: clarify expected interactions with LLMs Paolo Abeni
2026-07-24 10:22   ` Nicolai Buchwitz
2026-07-24 11:56   ` Jakub Raczynski
2026-07-24 13:39     ` Matthieu Baerts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d9f57f7676bb223438298cf349359f49@tipi-net.de \
    --to=nb@tipi-net.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.