public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Cohen, Eugene" <eugene@hp.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Shaw, Kevin W" <kevin.w.shaw@intel.com>
Subject: Re: FDF Specification Updates for PI 1.6 Standalone MM Components
Date: Thu, 18 Oct 2018 01:47:31 +0000	[thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D52142336@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CS1PR8401MB118903E12730341AE8481F37B4FF0@CS1PR8401MB1189.NAMPRD84.PROD.OUTLOOK.COM>

Hi Eugene,

Could you help to file a bugzilla ? thanks.
Refer to https://github.com/tianocore/tianocore.github.io/wiki/Reporting-Issues 

Best Regards,
Zhu Yonghong


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Cohen, Eugene
Sent: Thursday, October 18, 2018 1:11 AM
To: edk2-devel@lists.01.org; Shaw, Kevin W <kevin.w.shaw@intel.com>
Subject: [edk2] FDF Specification Updates for PI 1.6 Standalone MM Components

The FDF spec appears to be missing definitions for the new PI 1.6 component types like MM_CORE_STANDALONE and MM_STANDALONE.

Is there a plan to update the spec to reflect these new types? 

See https://edk2-docs.gitbooks.io/edk-ii-fdf-specification/content/v/release/1.28/3_edk_ii_fdf_file_format/39_[rule]_sections.html#39-rule-sections


Thanks,

Eugene

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


  reply	other threads:[~2018-10-18  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 17:11 FDF Specification Updates for PI 1.6 Standalone MM Components Cohen, Eugene
2018-10-18  1:47 ` Zhu, Yonghong [this message]
2018-10-18 15:17   ` Cohen, Eugene
2018-10-18 23:49     ` 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=B9726D6DCCFB8B4CA276A9169B02216D52142336@SHSMSX103.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