public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"Dong, Eric" <eric.dong@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation.
Date: Thu, 9 Aug 2018 13:29:35 +0200	[thread overview]
Message-ID: <4fb40db5-0315-80b8-d9c6-7d1e11e65d9b@redhat.com> (raw)
In-Reply-To: <734D49CCEBEEF84792F5B80ED585239D5BDC96E8@SHSMSX104.ccr.corp.intel.com>

On 08/09/18 05:18, Ni, Ruiyu wrote:

> We've reviewed the whole producer/consumer code and came to the conclusion
> that 4GB/NVS restriction is unnecessary.

I'd like to comment on this from a workflow POV as well.

If you perform a detailed review of the code, that's great. However, in
that case, please do take the time to *document* the review *in detail*
in the commit message.

I assume you and Eric may have spent a few hours reviewing the code,
maybe drawing diagrams, using check lists, and so on. Why was none of
that documented in the commit message?

The commit message stated the result of your investigation, and none of
the evidence. In order to review the patch, I had to rebuild the entire
argument from zero, checking the life-cycle of every single field in
ACPI_CPU_DATA, and that took the better part of a day.

My job as a reviewer is to *read* your investigation and verify it, not
to *reconstruct* it from scratch.

Documenting one's findings in detail also helps one root out omissions
or mistakes in one's reasoning. I catch my own errors like this all the
time.

Thanks
Laszlo


      parent reply	other threads:[~2018-08-09 11:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  7:40 [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Eric Dong
2018-08-08  7:40 ` [Patch v2 2/2] UefiCpuPkg/CpuS3DataDxe: Change Memory Type and address limitation Eric Dong
2018-08-08 16:55   ` Laszlo Ersek
2018-08-09  3:22     ` Ni, Ruiyu
2018-08-10  3:39     ` Dong, Eric
2018-08-10  4:00       ` 答复: " Fan Jeff
2018-08-10  4:01         ` 答复: " Fan Jeff
2018-08-08 14:45 ` [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Combine implementation Laszlo Ersek
2018-08-08 21:28 ` Laszlo Ersek
2018-08-09  3:18   ` Ni, Ruiyu
2018-08-09 11:21     ` Laszlo Ersek
2018-08-10  3:10       ` Dong, Eric
2018-08-09 11:29     ` Laszlo Ersek [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4fb40db5-0315-80b8-d9c6-7d1e11e65d9b@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox