From: "Rebecca Cran" <quic_rcran@quicinc.com>
To: <devel@edk2.groups.io>, <afish@apple.com>, <quic_rcran@quicinc.com>
Cc: Mike Kinney <michael.d.kinney@intel.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] MdePkg: Use ANSI colors to indicate debug message severity
Date: Thu, 1 Sep 2022 16:46:55 -0600 [thread overview]
Message-ID: <e2833fb3-c2e7-282f-2c7b-b6f6fc8d5d76@quicinc.com> (raw)
In-Reply-To: <C3548E14-359B-403C-812E-6BB7DD9426F2@apple.com>
On 9/1/22 16:21, Andrew Fish via groups.io wrote:
> I think this feature flag is going to control the output of edk2
> DEBUG. In an abstract sense DEBUG is not Terminal or ConOut. It could
> be mapped to the same device, but it does not have to be.
>
> So maybe PcdDebugAnsiSeqSupport or DebugLibAnsiSeqSupport?
Thanks, that makes more sense. I'll send out a v3 patch with
PcdDebugAnsiSeqSupport.
--
Rebecca Cran
prev parent reply other threads:[~2022-09-01 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 22:12 [PATCH 1/1] MdePkg: Use ANSI colors to indicate debug message severity Rebecca Cran
2022-08-29 23:29 ` Michael D Kinney
2022-09-01 21:52 ` Rebecca Cran
2022-09-01 22:21 ` [edk2-devel] " Andrew Fish
2022-09-01 22:46 ` 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=e2833fb3-c2e7-282f-2c7b-b6f6fc8d5d76@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