linux-kernel - Re: [PATCH v5 0/2] EDAC/ghes: refactor memory error reporting to avoid code duplication

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: <5D5735C8-3922-49D9-9DD0-605746B5CCE4@alien8.de>
Date:   Wed, 26 Jan 2022 10:16:28 +0000
From:   Boris Petkov <bp@...en8.de>
To:     Shuai Xue <xueshuai@...ux.alibaba.com>
CC:     rric@...nel.org, mchehab@...nel.org,
        zhangliguang@...ux.alibaba.com, tony.luck@...el.com,
        james.morse@....com, linux-edac@...r.kernel.org,
        linux-efi@...r.kernel.org, ardb@...nel.org,
        linux-kernel@...r.kernel.org, zhuo.song@...ux.alibaba.com
Subject: Re: [PATCH v5 0/2] EDAC/ghes: refactor memory error reporting to avoid code duplication

On January 26, 2022 9:26:01 AM UTC, Shuai Xue <xueshuai@...ux.alibaba.com> wrote:
>By the way, I have a question about review process: after waiting for a period
>of time, how can I tell whether you have no comments or are still in review process?
>

A good sign for when review is done is to wait to see replies to every patch.

BUT, there are other people on CC too so they would need to get a chance to have a look too.

Regardless, you wait for a week and then you incorporate all review comments and resend - not before.

This constant spamming with the patchset is not productive. You're not the only one who sends patches and wants review - you should consider that there are others who would need to get reviewed too.

-- 
Sent from a small device: formatting sux and brevity is inevitable.