public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael Brown" <mcb30@ipxe.org>
To: devel@edk2.groups.io, lersek@redhat.com, "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] [PATCH] UefiCpuPkg/PiSmmCpu: Remove hardcode 48 address size limitation
Date: Thu, 20 May 2021 12:11:22 +0100	[thread overview]
Message-ID: <2891abbe-9df7-a2bc-a306-449910167513@ipxe.org> (raw)
In-Reply-To: <e9854957-5380-8f9e-5c02-51fe1ec234ac@redhat.com>

On 18/05/2021 19:42, Laszlo Ersek wrote:
> On 05/18/21 09:51, Ni, Ray wrote:
>> Thanks for explaining why you don't think it's a good patch. I thought anytime changing a code,
>> I should try to make it better, functional better, looks better.
> 
> My only point was that separate concerns should be implemented in
> separate patches, or at least (if they are really difficult, or
> overkill, to isolate) that they should be documented.
> 
> Please try to think with your reviewers' mindsets in mind, when
> preparing a patch (commit message and code both). The question the patch
> author has to ask themselves is not only "how do I implement this", but
> also "how do I explain this to my reviewers".

(Apologies in advance for intruding.)

Ray: I think you may be neglecting one half of the problem.

When making a code change, there are (at least) two requirements:

1. The new version of the code must make sense.  You are definitely 
achieving this: as you say, "make it better, functional better, looks 
better".  This is good.

2. The *change* between the old and new versions of the code (i.e. the 
patch and accompanying commit message) must also make sense.  This is 
the requirement that I think Laszlo would like you to meet.

It's not viable for anyone to meaningfully review code unless both of 
these requirements are met.

Thanks,

Michael

      parent reply	other threads:[~2021-05-20 11:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12  4:53 [PATCH] UefiCpuPkg/PiSmmCpu: Remove hardcode 48 address size limitation Ni, Ray
2021-05-13  3:32 ` Dong, Eric
2021-05-14 10:55 ` [edk2-devel] " Laszlo Ersek
2021-05-15  0:04   ` Ni, Ray
2021-05-16  1:39     ` Laszlo Ersek
2021-05-18  7:51       ` Ni, Ray
2021-05-18 18:42         ` Laszlo Ersek
2021-05-20  4:28           ` Ni, Ray
2021-05-20  7:50             ` Laszlo Ersek
2021-05-20 11:11           ` Michael Brown [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=2891abbe-9df7-a2bc-a306-449910167513@ipxe.org \
    --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