public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
	"'leif.lindholm@linaro.org'" <leif.lindholm@linaro.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"'afish@apple.com'" <afish@apple.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: Patch List for 201911 stable tag
Date: Tue, 19 Nov 2019 18:50:19 +0100	[thread overview]
Message-ID: <48a7f95e-1028-ea52-9980-da7af871cef2@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E5437BA@SHSMSX104.ccr.corp.intel.com>

On 11/19/19 15:25, Gao, Liming wrote:
> Hi Stewards and all:
>   I collect current patch lists in devel mail list. Those patch
>   contributors request to add them for 201911 stable tag. Because the
>   time is close to Hard Feature Freeze, I want to collect your
>   feedback for below patches.
>
> Feature List (those all have pass code review):
> https://edk2.groups.io/g/devel/message/50602 [PATCH V2] BaseTools: Add [packages] section in dsc file

This patch can be merged during the Soft Feature Freeze. It was posted
before the Soft Feature Freeze, and also reviewed (by Bob, i.e. a
BaseTools Maintainer) before the Soft Feature Freeze.

As far as I can see, there is still an outstanding question from you, to
Zhiju ("Can you show what test are done for this new support?"), so I
think we should await the response to that.

Note that the patch should not be merged once the Hard Feature Freeze
starts, so there are ~3 days for Zhiju to answer the question about
testing (and for you to acknowledge that you are OK with the reply).

> Bug List (those all have pass code review):
> https://edk2.groups.io/g/devel/message/50625 [PATCH v1] MdeModulePkg/NvmExpressDxe: Fix wrong queue size for async IO queues

Looks very much like a bugfix to me, so it's suitable for merging even
during the Hard Feature Freeze.

> https://edk2.groups.io/g/devel/message/50406 [PATCH 1/1] MdePkg/Include: Add missing definitions of SMBIOS type 42h in SmBios.h

Based on Abner's response in the thread, this change does not appear
necessary for fixing actual functionality bugs; it rather completes a
previously incomplete feature addition. And Abner is not in a rush to
catch the upcoming stable tag with the patch. I suggest to delay it.

If others disagree, I won't insist; the above is just my preference.

> https://edk2.groups.io/g/devel/message/50661 [PATCH] UefiCpuPkg: Update the coding styles

Hmmm, quite undecided on this one. Does not fix a functionality bug
either, but what it fixes *are* a coding style bugs, and the patch is
low risk. I'm leaning towards merging it.

> https://edk2.groups.io/g/devel/message/50662 [PATCH] MdePkg: Update the comments of IsLanguageSupported

This was even reviewed by a package maintainer (= you) before the SFF,
so it can definitely go in.

> https://edk2.groups.io/g/devel/message/50663 [PATCH 0/3] Add missing strings for uni files

First of all, the structure of this series is wrong; please see my
feedback here:

  https://edk2.groups.io/g/devel/message/50666

(The two patches discussed just above were incorrectly included in the
same posting.)

Second, the three patches for the UNI files add too much brand new text
for my taste, for them to be considered bugfixes. The patches were
posted in time for the SFF, but the maintainer reviews came too late:

  https://edk2.groups.io/g/devel/message/50872
  https://edk2.groups.io/g/devel/message/50869
  https://edk2.groups.io/g/devel/message/50870

I suggest postponing.

> https://edk2.groups.io/g/devel/message/50866 [PATCH V1 0/2] Improve PeiInstallPeiMemory() description

I'm seriously confused by the subject prefixes in this patch thread.
What's going on with the version numbers?

  [edk2-devel] [PATCH V1 0/2] Improve PeiInstallPeiMemory() description
  [edk2-devel] [PATCH V3 1/2] MdeModulePkg PeiCore: Improve PeiInstallPeiMemory() description
  [edk2-devel] [PATCH V1 2/2] MdePkg PiPeiCis.h: Improve PeiInstallPeiMemory() description

Other than that... I'm torn. I guess I could be convinced that these
patches are indeed bugfixes, so I'm leaning towards merging them.

> https://edk2.groups.io/g/devel/message/50841 [PATCH V2 1/1] MdeModulePkg PeiCore: Fix typos

Personally I'm not happy about this patch. It's way too large for my taste:

 MdeModulePkg/Core/Pei/PeiMain.inf             | 10 ++--
 MdeModulePkg/Core/Pei/FwVol/FwVol.h           | 20 +++----
 MdeModulePkg/Core/Pei/PeiMain.h               | 52 ++++++++--------
 MdeModulePkg/Core/Pei/Dependency/Dependency.c | 12 ++--
 MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c | 51 ++++++++--------
 MdeModulePkg/Core/Pei/FwVol/FwVol.c           | 63 ++++++++++----------
 MdeModulePkg/Core/Pei/Hob/Hob.c               |  4 +-
 MdeModulePkg/Core/Pei/Image/Image.c           | 10 ++--
 MdeModulePkg/Core/Pei/Memory/MemoryServices.c | 18 +++---
 MdeModulePkg/Core/Pei/PeiMain/PeiMain.c       |  2 +-
 MdeModulePkg/Core/Pei/Ppi/Ppi.c               |  4 +-
 MdeModulePkg/Core/Pei/Security/Security.c     | 12 ++--
 12 files changed, 129 insertions(+), 129 deletions(-)

and it mixes multiple kinds of changes:

"Fixes typos and clarifies some wording throughout PeiCore."

When reviewing such a patch, the reviewer has a difficult time telling
apart purely syntactic (typo) fixes from semantic (wording) fixes. As a
reviewer I would suggest splitting this patch at least in two (typos vs.
semantics). Then I could be convinced such a set of two patches is
purely a bugfix.

I'm leaning towards "postpone" on this one, but I can see why people
would think "that's arbitrary". I guess I'll have to defer to others in
this instance.

Thanks
Laszlo


  reply	other threads:[~2019-11-19 17:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 14:25 Patch List for 201911 stable tag Liming Gao
2019-11-19 17:50 ` Laszlo Ersek [this message]
2019-11-19 19:01   ` Leif Lindholm
2019-11-20  1:46     ` [edk2-devel] " Wu, Hao A
2019-11-20 14:52     ` Liming Gao
     [not found]     ` <15D8E68889A9A669.17632@groups.io>
2019-11-21  8:57       ` Liming Gao
2019-11-21 10:37         ` Leif Lindholm
2019-11-21 17:26           ` Laszlo Ersek
2019-11-25  7:36             ` Bob Feng

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=48a7f95e-1028-ea52-9980-da7af871cef2@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