public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "Fan, ZhijuX" <zhijux.fan@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Feng, Bob C" <bob.c.feng@intel.com>
Subject: Re: [PATCH] Build Spec:Add Module Arch to BuildRebuild Module Section
Date: Fri, 26 Jul 2019 06:31:18 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4C274A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <FAD0D7E0AE0FA54D987F6E72435CAFD50AFA30CF@SHSMSX101.ccr.corp.intel.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: Fan, ZhijuX
>Sent: Friday, July 26, 2019 10:30 AM
>To: devel@edk2.groups.io
>Cc: Gao, Liming <liming.gao@intel.com>; Feng, Bob C <bob.c.feng@intel.com>
>Subject: [PATCH] Build Spec:Add Module Arch to BuildRebuild Module Section
>
>BZ:https://bugzilla.tianocore.org/show_bug.cgi?id=2022
>
>Added arch output to build report so it's easy to tell
>which arch is being generated. Code change
>https://bugzilla.tianocore.org/show_bug.cgi?id=2016
>will be done.The spec change is also required.
>
>Cc: Bob Feng <bob.c.feng@intel.com>
>Cc: Liming Gao <liming.gao@intel.com>
>Signed-off-by: Zhiju.Fan <zhijux.fan@intel.com>
>---
> 13_build_reports/138_module_section.md | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
>diff --git a/13_build_reports/138_module_section.md
>b/13_build_reports/138_module_section.md
>index d457c24..6f7edc5 100644
>--- a/13_build_reports/138_module_section.md
>+++ b/13_build_reports/138_module_section.md
>@@ -38,11 +38,12 @@ sections are listed according to their DSC position.
>
> ### 13.8.1 Module Section Summary
>
>-This sub-section lists the module basic information: Module name, INF file
>-path, File GUID, Size, hash value, module build time stamp, module build
>time
>-and driver type.
>+This sub-section lists the module basic information: Module name, Module
>Arch,
>+INF file path, File GUID, Size, hash value, module build time stamp, module
>+build time and driver type.
>
> * Module Name : %`BASE_NAME` in INF `[Defines]` section%
>+* Module Arch : %Architecture of current module%
> * Module INF Path : %Path of Module INF file%
> * File GUID : %`FILE_GUID` in INF `[Defines]` section%
> * Size : %Module EFI image size%
>@@ -70,6 +71,7 @@ Volume 3 of the PI Specification (Table 3 Defined File
>Types).
> >==========================================================
>================<
> Module Summary
> Module Name:        SmbiosDxe
>+Module Arch:        X64
> Module INF Path:    MdeModule\Universal\SmbiosDxe\SmbiosDxe.inf
> File GUID:          F9D88642-0737-49BC-81B5-6889CD57D9EA
> Size:               0x7000 (28.00K)
>@@ -88,6 +90,7 @@ Driver Type:        0x7 (DRIVER)
> >==========================================================
>================<
> Module Summary
> Module Name:        EbcDxe
>+Module Arch:        X64
> Module INF Path:    MdeModule\Universal\EbcDxe\EbcDxe.inf
> File GUID:          13AC6DD0-73D0-11D4-B06B-00AA00BD6DE7
> Size:               0x9000 (36.00K)
>--
>2.14.1.windows.1


      reply	other threads:[~2019-07-26  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  2:30 [PATCH] Build Spec:Add Module Arch to BuildRebuild Module Section Fan, ZhijuX
2019-07-26  6:31 ` Liming Gao [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E4C274A@SHSMSX104.ccr.corp.intel.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