From: "Wang, Yin" <yin.wang@intel.com>
To: Sunil V L <sunilvl@ventanamicro.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg:Fix Hii form name mismatch with EFI variable
Date: Tue, 8 Aug 2023 01:44:35 +0000 [thread overview]
Message-ID: <PH7PR11MB798598BD648CE8B5943ABEC2800DA@PH7PR11MB7985.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ZNDdP+V52VRR11qd@sunil-laptop>
Hi Sunil,
I will be providing a detailed update soon, along with a new version. Thank you for your careful review and comments.
Best regards,
Yin
-----Original Message-----
From: Sunil V L <sunilvl@ventanamicro.com>
Sent: Monday, August 7, 2023 8:02 PM
To: devel@edk2.groups.io; Wang, Yin <yin.wang@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg:Fix Hii form name mismatch with EFI variable
Hi Wang,
Thanks for the patch!
It will be good if you add versions to the patch subject. Even if you go back to v1, better to send as v3 with the change log.
On Fri, Jul 14, 2023 at 04:59:48PM +0800, Wang, Yin wrote:
> Onemore need change beside fixs:16acacf24c ("OvmfPkg: fix
> PlatformConfig")
fixs -> Fixes? Why don't we need "Fixes:" tag to either aefcc91805fd or 16acacf24c2c?
I think it is better to have commit message with exact error or information on what is the issue instead of just pointing to another commit.
> Find by sct case:ExtractConfigConformance fail.
>
> Signed-off-by: Yin Wang <yin.wang@intel.com>
> ---
> OvmfPkg/PlatformDxe/Platform.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/OvmfPkg/PlatformDxe/Platform.c
> b/OvmfPkg/PlatformDxe/Platform.c index cd3bfd554c98..c32439683d83
> 100644
> --- a/OvmfPkg/PlatformDxe/Platform.c
> +++ b/OvmfPkg/PlatformDxe/Platform.c
> @@ -279,7 +279,7 @@ ExtractConfig (
> //
> ConfigRequestHdr = HiiConstructConfigHdr (
> &gOvmfPlatformConfigGuid,
> - mVariableName,
> + mHiiFormName,
> mImageHandle
The code change LGTM.
Acked-by: Sunil V L <sunilvl@ventanamicro.com>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#107628): https://edk2.groups.io/g/devel/message/107628
Mute This Topic: https://groups.io/mt/100142143/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-08-08 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1689314786.git.yin.wang@intel.com>
2023-07-14 8:59 ` [PATCH 1/1] OvmfPkg:Fix Hii form name mismatch with EFI variable Wang, Yin
2023-07-17 2:52 ` [edk2-devel] " Wang, Yin
2023-07-17 11:36 ` Gerd Hoffmann
2023-07-20 0:57 ` Wang, Yin
2023-08-07 12:02 ` Sunil V L
2023-08-08 1:44 ` Wang, Yin [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=PH7PR11MB798598BD648CE8B5943ABEC2800DA@PH7PR11MB7985.namprd11.prod.outlook.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