public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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] Clarify that values of unused PCD are not evaluated
Date: Fri, 26 May 2017 20:08:42 -0700	[thread overview]
Message-ID: <1495854522-20180-2-git-send-email-michael.d.kinney@intel.com> (raw)
In-Reply-To: <1495854522-20180-1-git-send-email-michael.d.kinney@intel.com>

https://bugzilla.tianocore.org/show_bug.cgi?id=481

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>
---
 13_build_reports/134_platform_summary.md | 5 +++++
 README.md                                | 1 +
 2 files changed, 6 insertions(+)

diff --git a/13_build_reports/134_platform_summary.md b/13_build_reports/134_platform_summary.md
index e6f2a15..0674141 100644
--- a/13_build_reports/134_platform_summary.md
+++ b/13_build_reports/134_platform_summary.md
@@ -140,6 +140,11 @@ The first line is required:
 Additional lines may be displayed showing default values when the value is not a
 default value.
 
+Since the PCDs in this section are not used by any module, the PCD value is not
+evaluated to determine if it is a valid value or in a value in a valid range.
+Instead, the PCD value from the DSC file, FDF file, or build option are
+displayed exactly as they were entered.
+
 ### Example
 
 ```
diff --git a/README.md b/README.md
index 16fcc4a..6b6d5b9 100644
--- a/README.md
+++ b/README.md
@@ -212,3 +212,4 @@ Copyright (c) 2008-2017, Intel Corporation. All rights reserved.
 |            | [#504](https://bugzilla.tianocore.org/show_bug.cgi?id=504) Update build report to support -Y HASH option                                                                                                                                                                                                                                                            |               |
 |            | [#508](https://bugzilla.tianocore.org/show_bug.cgi?id=508) Build Spec: Add sections to PCD report for PCDs only used in conditions PCDs that are not used anywhere                                                                                                                                                                                                  |               |
 |            | [#480](https://bugzilla.tianocore.org/show_bug.cgi?id=480) Build spec: add description for Override PCD value on the command line                                                                                                                                                                                                                                   |               |
+|            | [#481](https://bugzilla.tianocore.org/show_bug.cgi?id=481) Build Spec: add clarification for not used Pcd that build tool will not do additional checks on its value                                                                                                                                                                                                |               |
-- 
2.6.3.windows.1



  reply	other threads:[~2017-05-27  3:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27  3:08 [edk2-BuildSpecification PATCH] Clarify that values of unused PCD are not evaluated Michael Kinney
2017-05-27  3:08 ` Michael Kinney [this message]
2017-05-31  1: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=1495854522-20180-2-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