From: "Laszlo Ersek" <lersek@redhat.com>
To: pjones@redhat.com
Cc: devel@edk2.groups.io, Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Jordan Justen <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [edk2/master PATCHv1 1/1] OvmfPkg: Make SOURCE_DEBUG_ENABLE actually need to be set to TRUE
Date: Wed, 25 Sep 2019 01:43:02 +0200 [thread overview]
Message-ID: <9c6d70b5-fcd6-373f-973f-044d1338e47b@redhat.com> (raw)
In-Reply-To: <20190920184507.909884-1-pjones@redhat.com>
Hi Peter,
thanks for the patch. Two comments:
On 09/20/19 20:45, Peter Jones wrote:
> Currently some tests check the value of SOURCE_DEBUG_ENABLE, and some
> tests check if it's defined or not. Additionally, in UefiPayloadPkg as
> well as some other trees, we define it as FALSE in the .dsc file.
>
> This patch changes all of the Ovmf platforms to explicitly define it as
> FALSE by default, and changes all of the checks to test if the value is
> TRUE.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
(1) Please drop this line. (I cannot touch up this part for you.)
The Contributed-under line has not been necessary since
<https://bugzilla.tianocore.org/show_bug.cgi?id=1373> was fixed.
> Signed-off-by: Peter Jones <pjones@redhat.com>
> ---
> OvmfPkg/OvmfPkgIa32.dsc | 17 +++++++++--------
> OvmfPkg/OvmfPkgIa32.fdf | 2 +-
> OvmfPkg/OvmfPkgIa32X64.dsc | 19 ++++++++++---------
> OvmfPkg/OvmfPkgIa32X64.fdf | 2 +-
> OvmfPkg/OvmfPkgX64.dsc | 19 ++++++++++---------
> OvmfPkg/OvmfPkgX64.fdf | 2 +-
> OvmfPkg/OvmfXen.dsc | 17 +++++++++--------
> OvmfPkg/OvmfXen.fdf | 2 +-
> 8 files changed, 42 insertions(+), 38 deletions(-)
[...]
> diff --git a/OvmfPkg/OvmfPkgIa32.fdf b/OvmfPkg/OvmfPkgIa32.fdf
> index 785affeb90c8..c7622fcfb7b0 100644
> --- a/OvmfPkg/OvmfPkgIa32.fdf
> +++ b/OvmfPkg/OvmfPkgIa32.fdf
> @@ -260,7 +260,7 @@ [FV.DXEFV]
> INF MdeModulePkg/Universal/MemoryTest/NullMemoryTestDxe/NullMemoryTestDxe.inf
>
> INF OvmfPkg/SioBusDxe/SioBusDxe.inf
> -!ifndef $(SOURCE_DEBUG_ENABLE)
> +!if $(SOURCE_DEBUG_ENABLE) != TRUE
(2) Can you please write "== FALSE" here (in the other FDF files too)?
That has a tiny bit more precedent.
I'd be willing to fix up (2) for you just before pushing, but I can't
touch (1).
With (1) and (2) fixed, for v2:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks!
Laszlo
prev parent reply other threads:[~2019-09-24 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 18:45 [edk2/master PATCHv1 1/1] OvmfPkg: Make SOURCE_DEBUG_ENABLE actually need to be set to TRUE pjones
2019-09-24 23:43 ` Laszlo Ersek [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=9c6d70b5-fcd6-373f-973f-044d1338e47b@redhat.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