diff options
author | Jakub Kicinski | 2022-03-29 21:24:58 -0700 |
---|---|---|
committer | Paolo Abeni | 2022-03-31 10:49:38 +0200 |
commit | 8f785c1bb84f7c8ca07c408dc96e8d8358b02bb3 (patch) | |
tree | a1b2f3be2724b86c6a0ee859dc92ba799eeb6a4b /Documentation | |
parent | 5d84921ac750d2b2e42c7102890b978cb2c2729e (diff) |
docs: netdev: rephrase the 'Under review' question
The semantics of "Under review" have shifted. Reword the question
about it a bit and focus it on the response time.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/networking/netdev-FAQ.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/Documentation/networking/netdev-FAQ.rst b/Documentation/networking/netdev-FAQ.rst index e10a8140d642..00ac300ebe6a 100644 --- a/Documentation/networking/netdev-FAQ.rst +++ b/Documentation/networking/netdev-FAQ.rst @@ -116,10 +116,12 @@ patch. Patches are indexed by the ``Message-ID`` header of the emails which carried them so if you have trouble finding your patch append the value of ``Message-ID`` to the URL above. -The above only says "Under Review". How can I find out more? -------------------------------------------------------------- +How long before my patch is accepted? +------------------------------------- Generally speaking, the patches get triaged quickly (in less than -48h). So be patient. Asking the maintainer for status updates on your +48h). But be patient, if your patch is active in patchwork (i.e. it's +listed on the project's patch list) the chances it was missed are close to zero. +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. |