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-BuildSpecification PATCH 0/3] Add support for mixed PCD access
Date: Wed, 19 Apr 2017 13:37:25 -0700 [thread overview]
Message-ID: <1492634248-15292-1-git-send-email-michael.d.kinney@intel.com> (raw)
https://bugzilla.tianocore.org/show_bug.cgi?id=485
GitHub word diff view of the pathes in this series
* [1/3] https://github.com/mdkinney/edk2-BuildSpecification/commit/e972f4ae0135704243d04a6da2a177d9990d2340?w=1
* [2/3] https://github.com/mdkinney/edk2-BuildSpecification/commit/4192cda206dce5ca97264c992492998c47671563?w=1
* [3/3] https://github.com/mdkinney/edk2-BuildSpecification/commit/00707ca6de6872f59e2dace2dc5e4f9a93cca418?w=1
The build tools currently require a PCD to use the
same access method from all modules. This update
still requires modules built from sources to use
the same access method, but binary modules are
allowed to use alternate access methods.
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 (3):
Add rules for for mixed PCD access
Make room for new mixed PCD report section
Add report section for mixed PCD access
13_build_reports/133_output.md | 1 +
13_build_reports/135_global_pcd_section.md | 135 ------
13_build_reports/135_mixed_pcd_section.md | 54 +++
13_build_reports/136_fd_section.md | 166 --------
13_build_reports/136_global_pcd_section.md | 135 ++++++
13_build_reports/137_fd_section.md | 166 ++++++++
13_build_reports/137_module_section.md | 452 ---------------------
.../138_execution_order_prediction_section.md | 71 ----
13_build_reports/138_module_section.md | 452 +++++++++++++++++++++
.../139_execution_order_prediction_section.md | 71 ++++
.../84_auto-generated_pcd_database_file.md | 97 +++--
README.md | 1 +
SUMMARY.md | 9 +-
13 files changed, 939 insertions(+), 871 deletions(-)
delete mode 100644 13_build_reports/135_global_pcd_section.md
create mode 100644 13_build_reports/135_mixed_pcd_section.md
delete mode 100644 13_build_reports/136_fd_section.md
create mode 100644 13_build_reports/136_global_pcd_section.md
create mode 100644 13_build_reports/137_fd_section.md
delete mode 100644 13_build_reports/137_module_section.md
delete mode 100644 13_build_reports/138_execution_order_prediction_section.md
create mode 100644 13_build_reports/138_module_section.md
create mode 100644 13_build_reports/139_execution_order_prediction_section.md
--
2.6.3.windows.1
next reply other threads:[~2017-04-19 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 20:37 Michael Kinney [this message]
2017-04-19 20:37 ` [edk2-BuildSpecification PATCH 1/3] Add rules for for mixed PCD access Michael Kinney
2017-04-19 20:37 ` [edk2-BuildSpecification PATCH 2/3] Make room for new mixed PCD report section Michael Kinney
2017-04-19 20:37 ` [edk2-BuildSpecification PATCH 3/3] Add report section for mixed PCD access Michael Kinney
2017-04-20 3:06 ` Zhu, Yonghong
2017-04-20 4:15 ` Kinney, Michael D
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=1492634248-15292-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