From: Felix Polyudov <Felixp@ami.com>
To: "'Feng, Bob C'" <bob.c.feng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Liming Gao <liming.gao@intel.com>
Subject: Re: [Patch] Document: Update the INF spec about [Depex] section
Date: Thu, 28 Feb 2019 15:39:14 +0000 [thread overview]
Message-ID: <9333E191E0D52B4999CE63A99BA663A00302C69126@atlms1.us.megatrends.com> (raw)
In-Reply-To: <20190228021141.25544-1-bob.c.feng@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Feng, Bob C
> Sent: Wednesday, February 27, 2019 9:12 PM
> To: edk2-devel@lists.01.org
> Cc: Liming Gao
> Subject: [edk2] [Patch] Document: Update the INF spec about [Depex] section
>
> <GuidOrPcdStmt> ::= {"BEFORE"} {"AFTER"} <GuidOrPcdName> should be
> <GuidOrPcdStmt> ::= [{"BEFORE"} {"AFTER"}]<GuidOrPcdName>
>
> The "BEFORE" or "AFTER" is optional key words in current implementation.
The proposed definition implies that BEFORE and AFTER can be used at the same time, which is incorrect.
I think it should be
<GuidOrPcdStmt> ::= [{"BEFORE"} |{"AFTER"}]<GuidOrPcdName>
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Bob Feng <bob.c.feng@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> ---
> 3_edk_ii_inf_file_format/314_[depex]_sections.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/3_edk_ii_inf_file_format/314_[depex]_sections.md b/3_edk_ii_inf_file_format/314_[depex]_sections.md
> index 942bcf9..3c0820a 100644
> --- a/3_edk_ii_inf_file_format/314_[depex]_sections.md
> +++ b/3_edk_ii_inf_file_format/314_[depex]_sections.md
> @@ -179,11 +179,11 @@ and VOID* datum type, and the size of the PCD must be 16 bytes.
> <DxeDepexStatements> ::= {<SorStmt>} {<GuidOrPcdStmt>} {<BoolStmt>}
> <PeiDepex> ::= <PeiDepexStatements>*
> ["END" <EOL>]
> <PeiDepexStatements> ::= {<BoolStmt>} {<DepInstruct>}
> <SmmDepex> ::= <DxeDepex>
> -<GuidOrPcdStmt> ::= {"BEFORE"} {"AFTER"} <GuidOrPcdName> [<EOL>]
> +<GuidOrPcdStmt> ::= [{"BEFORE"} {"AFTER"}] <GuidOrPcdName> [<EOL>]
> <GuidOrPcdName> ::= {<GuidCName>} {<PcdName>}
> <DepInstruct> ::= "PUSH" <CFormatGUID> [<EOL>]
> <SorStmt> ::= "SOR" <BoolStmt> [<EOL>]
> <BoolStmt> ::= {<Bool>} {<BoolExpress>}
> <Bool> ::= {"TRUE"} {"FALSE"} {<GuidCName>} {<PcdName>} [<EOL>]
> --
> 2.20.1.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
Please consider the environment before printing this email.
The information contained in this message may be confidential and proprietary to American Megatrends, Inc. This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.
next prev parent reply other threads:[~2019-02-28 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 2:11 [Patch] Document: Update the INF spec about [Depex] section Feng, Bob C
2019-02-28 15:39 ` Felix Polyudov [this message]
2019-02-28 15:45 ` Carsey, Jaben
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=9333E191E0D52B4999CE63A99BA663A00302C69126@atlms1.us.megatrends.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