From: Michael Kinney <michael.d.kinney@intel.com>
To: edk2-devel@lists.01.org
Cc: Liming Gao <liming.gao@intel.com>,
Yonghong Zhu <yonghong.zhu@intel.com>,
Kevin W Shaw <kevin.w.shaw@intel.com>
Subject: [edk2-FdfSpecification Patch] IMAGE_TYPE_ID is required in [FmpPayload] section
Date: Wed, 5 Apr 2017 20:38:26 -0700 [thread overview]
Message-ID: <1491449907-6560-1-git-send-email-michael.d.kinney@intel.com> (raw)
https://bugzilla.tianocore.org/show_bug.cgi?id=426
Update the EBNF for [FmpPayload] in Section 3.8
so IMAGE_TYPE_ID is required and must always be assigned
to a valid registry format GUID value.
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
GitHub branch for review:
https://github.com/mdkinney/edk2-FdfSpecification/tree/Bugzilla_426_IMAGE_TYPE_ID_Required
GitHub branch compare against latest DRAFT for review:
https://github.com/tianocore-docs/edk2-FdfSpecification/compare/master...mdkinney:Bugzilla_426_IMAGE_TYPE_ID_Required?w=1
Michael Kinney (1):
IMAGE_TYPE_ID is required in [FmpPayload] section
3_edk_ii_fdf_file_format/38_[fmppayload]_sections.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.6.3.windows.1
next reply other threads:[~2017-04-06 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 3:38 Michael Kinney [this message]
2017-04-06 3:38 ` [edk2-FdfSpecification Patch] IMAGE_TYPE_ID is required in [FmpPayload] section Michael Kinney
2017-04-06 3:42 ` Zhu, Yonghong
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=1491449907-6560-1-git-send-email-michael.d.kinney@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