From: Mark Brown <broonie@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew@lunn.ch, corbet@lwn.net,
workflows@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: netdev: try to guide people on dealing with silence
Date: Mon, 20 Nov 2023 20:13:19 +0000 [thread overview]
Message-ID: <0d80ee23-e106-487e-a824-b048948a859a@sirena.org.uk> (raw)
In-Reply-To: <20231120200109.620392-1-kuba@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 611 bytes --]
On Mon, Nov 20, 2023 at 12:01:09PM -0800, Jakub Kicinski wrote:
> +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::
> + 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?
This bit (modulo the reference to patchwork) feels like it's generically
good advice and could find a home in submitting-patches.rst or similar,
not that it isn't worth repeating here.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-11-20 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:01 [PATCH net] docs: netdev: try to guide people on dealing with silence Jakub Kicinski
2023-11-20 20:13 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-18 17:24 Jakub Kicinski
2023-11-18 19:09 ` Andrew Lunn
2023-11-18 23:22 ` Jakub Kicinski
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=0d80ee23-e106-487e-a824-b048948a859a@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andrew@lunn.ch \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=workflows@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).