linux-kernel - Re: [PATCH 0/3] Documentation fixes for MT6370 RGB

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: <da9d9bca-23d5-aaa8-a815-5a9421c05a3d@gmail.com>
Date:   Thu, 23 Mar 2023 19:35:42 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Lee Jones <lee@...nel.org>
Cc:     Linux Documentation <linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        Linux MediaTek <linux-mediatek@...ts.infradead.org>,
        Linux LEDs <linux-leds@...r.kernel.org>,
        Jonathan Corbet <corbet@....net>,
        Matthias Brugger <matthias.bgg@...il.com>,
        AngeloGioacchino Del Regno 
        <angelogioacchino.delregno@...labora.com>,
        Shuah Khan <skhan@...uxfoundation.org>,
        ChiaEn Wu <chiaen_wu@...htek.com>,
        ChiYuan Huang <cy_huang@...htek.com>
Subject: Re: [PATCH 0/3] Documentation fixes for MT6370 RGB

On 3/23/23 19:31, Lee Jones wrote:
>> ping
> 
> a) Don't do that!
> 
> b) Especually don't do that 4 days after submission!
> 
> The usual expectation is 2 full weeks before submitting a [RESEND].
> 
> Mark Brown says it best:
> 
> "
> Please don't send content free pings and please allow a reasonable time
> for review.  People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review.  If there have been
> review comments then people may be waiting for those to be addressed.
> 
> Sending content free pings adds to the mail volume (if they are seen at
> all) which is often the problem and since they can't be reviewed
> directly if something has gone wrong you'll have to resend the patches
> anyway, so sending again is generally a better approach though there are
> some other maintainers who like them - if in doubt look at how patches
> for the subsystem are normally handled.
> "
> 

Ah! I triggered the wrong message at the wrong time. Thanks anyway!

-- 
An old man doll... just what I always wanted! - Clara