From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Shaw, Kevin W" <kevin.w.shaw@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [edk2-InfSpecification PATCH] Clarify that PCD values may come from the build command line
Date: Wed, 31 May 2017 01:52:00 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51E8AF9C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1495848919-36844-1-git-send-email-michael.d.kinney@intel.com>
Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com>
Best Regards,
Zhu Yonghong
-----Original Message-----
From: Kinney, Michael D
Sent: Saturday, May 27, 2017 9:35 AM
To: edk2-devel@lists.01.org
Cc: Gao, Liming <liming.gao@intel.com>; Zhu, Yonghong <yonghong.zhu@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
Subject: [edk2-InfSpecification PATCH] Clarify that PCD values may come from the build command line
GitHub branch for review:
* https://github.com/mdkinney/edk2-InfSpecification/tree/Bugzilla_522_AddPcdValueFromCommandLine
GitHub word diff view of the patches in this series:
* [1/1] https://github.com/mdkinney/edk2-InfSpecification/commit/a7412993bd49ded0cc7069913bc5008d782a3597?w=1
https://bugzilla.tianocore.org/show_bug.cgi?id=522
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>
Michael Kinney (1):
Clarify that PCD values may come from the build command line
2_inf_overview/214_pcd_sections.md | 7 ++++---
README.md | 3 ++-
2 files changed, 6 insertions(+), 4 deletions(-)
--
2.6.3.windows.1
prev parent reply other threads:[~2017-05-31 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 1:35 [edk2-InfSpecification PATCH] Clarify that PCD values may come from the build command line Michael Kinney
2017-05-27 1:35 ` Michael Kinney
2017-05-31 1:52 ` Zhu, Yonghong [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=B9726D6DCCFB8B4CA276A9169B02216D51E8AF9C@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