netdev - Re: [PATCH net v2 07/14] docs: netdev: rephrase the 'Under review' question

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 29 Mar 2022 20:33:05 -0700
From:   Florian Fainelli <f.fainelli@...il.com>
To:     Jakub Kicinski <kuba@...nel.org>, davem@...emloft.net
Cc:     netdev@...r.kernel.org, pabeni@...hat.com, corbet@....net,
        bpf@...r.kernel.org, linux-doc@...r.kernel.org, andrew@...n.ch
Subject: Re: [PATCH net v2 07/14] docs: netdev: rephrase the 'Under review'
 question



On 3/28/2022 10:08 PM, Jakub Kicinski wrote:
> 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@...nel.org>

Reviewed-by: Florian Fainelli <f.fainelli@...il.com>

Nit below:

> ---
>   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 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.

I would reword that at some point, this feels a little bit retaliating.
-- 
Florian