From: "Laszlo Ersek" <lersek@redhat.com>
To: Michael D Kinney <michael.d.kinney@intel.com>, devel@edk2.groups.io
Cc: Liming Gao <gaoliming@byosoft.com.cn>,
Aaron Li <aaron.li@intel.com>, Liu Yun <yun.y.liu@intel.com>,
Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] [Patch v3 2/2] MdeModulePkg/Core/Dxe: Set MemoryTypeInfo bin range from HOB
Date: Tue, 30 Jan 2024 17:39:40 +0100 [thread overview]
Message-ID: <46bb68d3-4a33-a880-4b67-758c5d5153ec@redhat.com> (raw)
In-Reply-To: <20240129185808.776-3-michael.d.kinney@intel.com>
On 1/29/24 19:58, Michael D Kinney wrote:
> + if (mMemoryTypeInformationInitialized) {
> + DEBUG ((DEBUG_ERROR, "CoreSetMemoryTypeInformationRange() ignored. Bins already set."));
> + return;
> + }
Two suggestions for the DEBUG:
- %a with __func__ is shorter / more robust than open-coding the
function name
- a newline character \n is missing from the end of the message.
I think just these comments don't need a v4 posting; I'd suggest editing
the patch upon merge.
Series
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks!
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#114802): https://edk2.groups.io/g/devel/message/114802
Mute This Topic: https://groups.io/mt/104038200/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-01-30 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 18:58 [edk2-devel] [Patch v3 0/2] MdeModulePkg/Core/Dxe: Set MemoryTypeInfo bin range from HOB Michael D Kinney
2024-01-29 18:58 ` [edk2-devel] [Patch v3 1/2] MdeModulePkg/Core/Dxe: Initialize GCD before RT memory allocations Michael D Kinney
2024-01-29 18:58 ` [edk2-devel] [Patch v3 2/2] MdeModulePkg/Core/Dxe: Set MemoryTypeInfo bin range from HOB Michael D Kinney
2024-01-30 16:39 ` 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=46bb68d3-4a33-a880-4b67-758c5d5153ec@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