From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, pabeni@redhat.com, corbet@lwn.net,
bpf@vger.kernel.org, linux-doc@vger.kernel.org, andrew@lunn.ch,
f.fainelli@gmail.com, Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net v3 08/14] docs: netdev: rephrase the 'should I update patchwork' question
Date: Tue, 29 Mar 2022 21:24:59 -0700 [thread overview]
Message-ID: <20220330042505.2902770-9-kuba@kernel.org> (raw)
In-Reply-To: <20220330042505.2902770-1-kuba@kernel.org>
Make the question shorter and adjust the start of the answer accordingly.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
Documentation/networking/netdev-FAQ.rst | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst
index 00ac300ebe6a..9c455d08510d 100644
--- a/Documentation/networking/netdev-FAQ.rst
+++ b/Documentation/networking/netdev-FAQ.rst
@@ -125,9 +125,11 @@ Asking the maintainer for status updates on your
patch is a good way to ensure your patch is ignored or pushed to the
bottom of the priority list.
-I submitted multiple versions of the patch series. Should I directly update patchwork for the previous versions of these patch series?
---------------------------------------------------------------------------------------------------------------------------------------
-No, please don't interfere with the patch status on patchwork, leave
+Should I directly update patchwork state of my own patches?
+-----------------------------------------------------------
+It may be tempting to help the maintainers and update the state of your
+own patches when you post a new version or spot a bug. Please do not do that.
+Interfering with the patch status on patchwork will only cause confusion. Leave
it to the maintainer to figure out what is the most recent and current
version that should be applied. If there is any doubt, the maintainer
will reply and ask what should be done.
--
2.34.1
next prev parent reply other threads:[~2022-03-30 4:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 4:24 [PATCH net v3 00/14] docs: update and move the netdev-FAQ Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 01/14] docs: netdev: replace references to old archives Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 02/14] docs: netdev: minor reword Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 03/14] docs: netdev: move the patch marking section up Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 04/14] docs: netdev: turn the net-next closed into a Warning Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 05/14] docs: netdev: note that RFC postings are allowed any time Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 06/14] docs: netdev: shorten the name and mention msgid for patch status Jakub Kicinski
2022-03-30 4:24 ` [PATCH net v3 07/14] docs: netdev: rephrase the 'Under review' question Jakub Kicinski
2022-03-30 4:24 ` Jakub Kicinski [this message]
2022-03-30 23:40 ` [PATCH net v3 08/14] docs: netdev: rephrase the 'should I update patchwork' question Florian Fainelli
2022-03-30 4:25 ` [PATCH net v3 09/14] docs: netdev: add a question about re-posting frequency Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 10/14] docs: netdev: make the testing requirement more stringent Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 11/14] docs: netdev: add missing back ticks Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 12/14] docs: netdev: call out the merge window in tag checking Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 13/14] docs: netdev: broaden the new vs old code formatting guidelines Jakub Kicinski
2022-03-30 4:25 ` [PATCH net v3 14/14] docs: netdev: move the netdev-FAQ to the process pages Jakub Kicinski
2022-03-31 9:30 ` [PATCH net v3 00/14] docs: update and move the netdev-FAQ patchwork-bot+netdevbpf
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=20220330042505.2902770-9-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 NNTP newsgroup(s).