From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
Andrew Fish <afish@apple.com>
Subject: Re: [PATCH v3 1/1] MdePkg: Use ANSI colors to indicate debug message severity
Date: Tue, 6 Sep 2022 15:51:43 -0600 [thread overview]
Message-ID: <18be95c4-15ea-4e4c-3638-3357293b0bcd@quicinc.com> (raw)
In-Reply-To: <CO1PR11MB4929F09FB21564102CCCF8F6D27E9@CO1PR11MB4929.namprd11.prod.outlook.com>
On 9/6/22 12:40, Kinney, Michael D wrote:
> Rebecca,
>
> BasePrintLib is used for much more than just DEBUG() macros. This features should
> not modify the behavior of BasePrintLib.
>
> For example, a single module that links to BasePrintLib can use those services
> for non DebugLib services with no expectation that ANSI sequences are added
> and that same module can link against DebugLib for DEBUG() macro support that
> expects ANSI sequences to be added. This is a conflict.
>
> The scope of this change should be only the DebugLib instance.
The reason I put the functions in BasePrintLib is because I couldn't see
any other common location to put them.
But since one deals with Unicode and the other ASCII, I think defining
them in their respective libraries might be fine, since we won't end up
duplicating code.
>> [PcdsFeatureFlag]
>> gEfiMdePkgTokenSpaceGuid.PcdUgaConsumeSupport|TRUE
>> + gEfiMdePkgTokenSpaceGuid.PcdDebugAnsiSeqSupport|FALSE
> The DEC default value is FALSE, so this line is not required.
Thanks, I'll fix it in the next patch version.
--
Rebecca Cran
prev parent reply other threads:[~2022-09-06 22:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 11:23 [PATCH v3 0/1] MdePkg: Use ANSI colors to indicate debug message severity Rebecca Cran
2022-09-02 11:23 ` [PATCH v3 1/1] " Rebecca Cran
2022-09-06 18:40 ` Michael D Kinney
2022-09-06 21:51 ` Rebecca Cran [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=18be95c4-15ea-4e4c-3638-3357293b0bcd@quicinc.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