public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "Feng, Bob C" <bob.c.feng@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [Patch] Document: Correct the Appendix G to Appendix F
Date: Tue, 7 May 2019 08:08:01 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E443FFF@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190428034525.13244-1-bob.c.feng@intel.com>

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

>-----Original Message-----
>From: Feng, Bob C
>Sent: Sunday, April 28, 2019 11:45 AM
>To: devel@edk2.groups.io
>Cc: Feng, Bob C <bob.c.feng@intel.com>; Gao, Liming <liming.gao@intel.com>
>Subject: [Patch] Document: Correct the Appendix G to Appendix F
>
>BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1690
>
>This patch is going to fix the typo of Appendix G in Inf spec.
>
>Signed-off-by: Bob Feng <bob.c.feng@intel.com>
>Cc: Liming Gao <liming.gao@intel.com>
>---
> 2_inf_overview/24_[defines]_section.md | 2 +-
> appendix_f_module_types.md             | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/2_inf_overview/24_[defines]_section.md
>b/2_inf_overview/24_[defines]_section.md
>index 54fa829..8949299 100644
>--- a/2_inf_overview/24_[defines]_section.md
>+++ b/2_inf_overview/24_[defines]_section.md
>@@ -84,11 +84,11 @@ implement functions that satisfy the
>BaseMemoryAllocation library class. In
> this instance, the driver module would also specify the `LIBRARY_CLASS` in
>the
> `[Defines]` section. Other DXE drivers that would require a library instance for
> the `BaseMemoryAllocation` class could specify the `DXE_CORE` INF file as the
> recommended instance for satisfying the required library class instance.
>
>-Appendix G lists the available `MODULE_TYPE` values supported by EDK II INF
>+Appendix F lists the available `MODULE_TYPE` values supported by EDK II INF
> files.
>
> The EDK II `[Defines]` section is common to all architectures and does not
> permit using architectural modifiers in the section tag name.
>
>diff --git a/appendix_f_module_types.md b/appendix_f_module_types.md
>index 334d4b7..7082332 100644
>--- a/appendix_f_module_types.md
>+++ b/appendix_f_module_types.md
>@@ -1,7 +1,7 @@
> <!--- @file
>-  Appendix G Module Types
>+  Appendix F Module Types
>
>   Copyright (c) 2007-2019, Intel Corporation. All rights reserved.<BR>
>
>   Redistribution and use in source (original document form) and 'compiled'
>   forms (converted to PDF, epub, HTML and other formats) with or without
>--
>2.20.1.windows.1


      reply	other threads:[~2019-05-07  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-28  3:45 [Patch] Document: Correct the Appendix G to Appendix F Bob Feng
2019-05-07  8:08 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E443FFF@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