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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87y1gjen5d.fsf@meer.lwn.net>
Date:   Tue, 03 Oct 2023 09:33:34 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Mark Brown <broonie@...nel.org>
Cc:     Javier Martinez Canillas <javier@...hile0.org>,
        workflows@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] docs: submitting-patches: Suggest a longer expected
 time for responses

Mark Brown <broonie@...nel.org> writes:

> While some subsystems do typically have very fast turnaround times on
> review this is far from standard over the kernel and is likely to set
> unrealistic expectations for submitters.  Tell submitters to expect 2-3
> weeks instead, this will cover more of the kernel.
>
> Signed-off-by: Mark Brown <broonie@...nel.org>
> ---
>  Documentation/process/submitting-patches.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)

I was hoping to see some more comments on this; it is a fairly
significant change in the expectations we put on our reviewers.  Oh
well, I've applied it.  I wonder if we should add a note saying to look
at the maintainer profile for the subsystem in question for more
specific guidance?  Of course, it would be good to have more of those...

Thanks,

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ