From: "Konstantin Aladyshev" <aladyshev22@gmail.com>
To: devel@edk2.groups.io
Cc: bob.c.feng@intel.com, gaoliming@byosoft.com.cn,
yuwei.chen@intel.com,
Konstantin Aladyshev <aladyshev22@gmail.com>
Subject: [PATCH 4/6] BaseTools/VolInfo: Update file and section type strings
Date: Tue, 30 Aug 2022 13:14:43 +0300 [thread overview]
Message-ID: <20220830101445.18110-4-aladyshev22@gmail.com> (raw)
In-Reply-To: <20220830101445.18110-1-aladyshev22@gmail.com>
Change SMM to MM in naming according to the recent PI specifications.
Remove trailing whitespaces in some strings.
Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
---
BaseTools/Source/C/VolInfo/VolInfo.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/BaseTools/Source/C/VolInfo/VolInfo.c b/BaseTools/Source/C/VolInfo/VolInfo.c
index d9be3d8c18..2d7c6212b3 100644
--- a/BaseTools/Source/C/VolInfo/VolInfo.c
+++ b/BaseTools/Source/C/VolInfo/VolInfo.c
@@ -676,11 +676,11 @@ Returns:
//
// 0x17
//
- "EFI_SECTION_FIRMWARE_VOLUME_IMAGE ",
+ "EFI_SECTION_FIRMWARE_VOLUME_IMAGE",
//
// 0x18
//
- "EFI_SECTION_FREEFORM_SUBTYPE_GUID ",
+ "EFI_SECTION_FREEFORM_SUBTYPE_GUID",
//
// 0x19
//
@@ -696,7 +696,7 @@ Returns:
//
// 0x1C
//
- "EFI_SECTION_SMM_DEPEX",
+ "EFI_SECTION_MM_DEPEX",
//
// 0x1C+
//
@@ -1282,7 +1282,7 @@ Returns:
break;
case EFI_FV_FILETYPE_SMM:
- printf ("EFI_FV_FILETYPE_SMM\n");
+ printf ("EFI_FV_FILETYPE_MM\n");
break;
case EFI_FV_FILETYPE_FIRMWARE_VOLUME_IMAGE:
@@ -1290,11 +1290,11 @@ Returns:
break;
case EFI_FV_FILETYPE_COMBINED_SMM_DXE:
- printf ("EFI_FV_FILETYPE_COMBINED_SMM_DXE\n");
+ printf ("EFI_FV_FILETYPE_COMBINED_MM_DXE\n");
break;
case EFI_FV_FILETYPE_SMM_CORE:
- printf ("EFI_FV_FILETYPE_SMM_CORE\n");
+ printf ("EFI_FV_FILETYPE_MM_CORE\n");
break;
case EFI_FV_FILETYPE_MM_STANDALONE:
--
2.25.1
next prev parent reply other threads:[~2022-08-30 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 10:14 [PATCH 1/6] BaseTools/VolInfo: Fix EFI_SECTION_GUID_DEFINED parsing Konstantin Aladyshev
2022-08-30 10:14 ` [PATCH 2/6] BaseTools/VolInfo: Correct buffer for GenCrc32 tool Konstantin Aladyshev
2022-09-27 2:50 ` 回复: " gaoliming
2022-08-30 10:14 ` [PATCH 3/6] BaseTools/VolInfo: Increase GUID base name string Konstantin Aladyshev
2022-09-26 5:25 ` 回复: [edk2-devel] " gaoliming
2022-08-30 10:14 ` Konstantin Aladyshev [this message]
2022-09-26 5:26 ` 回复: [edk2-devel] [PATCH 4/6] BaseTools/VolInfo: Update file and section type strings gaoliming
2022-08-30 10:14 ` [PATCH 5/6] BaseTools/VolInfo: Parse apriori files Konstantin Aladyshev
2022-09-26 5:27 ` 回复: [edk2-devel] " gaoliming
2022-08-30 10:14 ` [PATCH 6/6] BaseTools/VolInfo: Update copyright information Konstantin Aladyshev
2022-09-26 5:27 ` 回复: [edk2-devel] " gaoliming
2022-08-31 1:43 ` 回复: [edk2-devel] [PATCH 1/6] BaseTools/VolInfo: Fix EFI_SECTION_GUID_DEFINED parsing gaoliming
2022-10-01 15:15 ` 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=20220830101445.18110-4-aladyshev22@gmail.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