From: Mark Brown Date: Wed, 13 Sep 2023 14:56:27 +0000 (+0100) Subject: docs: submitting-patches: Suggest a longer expected time for responses X-Git-Tag: v6.7-rc1~118^2~29 X-Git-Url: https://www.infradead.org/git/?a=commitdiff_plain;h=02f9998754b0;p=users%2Fdwmw2%2Flinux.git docs: submitting-patches: Suggest a longer expected time for responses 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 Reviewed-by: Javier Martinez Canillas Signed-off-by: Jonathan Corbet Link: https://lore.kernel.org/r/20230913-submitting-patches-delay-v1-1-a2d48c5ca205@kernel.org --- diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst index efac910e26590..3fcfa029c9b30 100644 --- a/Documentation/process/submitting-patches.rst +++ b/Documentation/process/submitting-patches.rst @@ -366,10 +366,10 @@ busy people and may not get to your patch right away. Once upon a time, patches used to disappear into the void without comment, but the development process works more smoothly than that now. You should -receive comments within a week or so; if that does not happen, make sure -that you have sent your patches to the right place. Wait for a minimum of -one week before resubmitting or pinging reviewers - possibly longer during -busy times like merge windows. +receive comments within a few weeks (typically 2-3); if that does not +happen, make sure that you have sent your patches to the right place. +Wait for a minimum of one week before resubmitting or pinging reviewers +- possibly longer during busy times like merge windows. It's also ok to resend the patch or the patch series after a couple of weeks with the word "RESEND" added to the subject line::