[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d89ffe0-6e34-a82d-09f0-9dd803fc256f@linux.alibaba.com>
Date: Wed, 26 Jan 2022 17:26:01 +0800
From: Shuai Xue <xueshuai@...ux.alibaba.com>
To: Borislav Petkov <bp@...en8.de>
Cc: rric@...nel.org, mchehab@...nel.org, tony.luck@...el.com,
james.morse@....com, ardb@...nel.org, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org,
zhangliguang@...ux.alibaba.com, zhuo.song@...ux.alibaba.com
Subject: Re: [PATCH v5 0/2] EDAC/ghes: refactor memory error reporting to
avoid code duplication
Hi, Borislav,
在 2022/1/26 PM4:20, Borislav Petkov 写道:
> On Wed, Jan 26, 2022 at 04:17:00PM +0800, Shuai Xue wrote:
>> ghes_edac_report_mem_error() in ghes_edac.c is a Long Method and have
>> Duplicated Code with cper_mem_err_location(), cper_dimm_err_location(), and
>> cper_mem_err_type_str() in drivers/firmware/efi/cper.c. In addition, the
>> cper_print_mem() in drivers/firmware/efi/cper.c only reports the error
>> status and misses its description.
>
> Dude, what about
>
> wait for a week or until the patchset has been fully reviewed
>
> don't you understand?!
>
> Please let me know what about the review process is not clear to you so
> that we can document it better.
Emmm, when I received your replied email, I thought you had fully reviewed them. So
I work to address your comments and reply as soon as possible. Sorry, I misunderstood.
Of course, I can wait. As I said before, take your time.
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?
Best Regards,
Shuai
Powered by blists - more mailing lists