From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Michal Orzel <michal.orzel@amd.com>, xen-devel@lists.xenproject.org
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
"Julien Grall" <julien@xen.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>,
"Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>
Subject: Re: [PATCH] xen: Append a newline character to panic() where missing
Date: Wed, 14 Jun 2023 09:04:45 +0100 [thread overview]
Message-ID: <261ab0b0-91ed-e6b7-730f-0ecb8a7b5635@citrix.com> (raw)
In-Reply-To: <20230614073018.21303-1-michal.orzel@amd.com>
On 14/06/2023 8:30 am, Michal Orzel wrote:
> Missing newline is inconsistent with the rest of the callers, since
> panic() expects it.
>
> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>
although...
> ---
> xen/arch/arm/bootfdt.c | 2 +-
> xen/arch/arm/domain_build.c | 6 +++---
> xen/arch/x86/cpu/microcode/core.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/xen/arch/arm/bootfdt.c b/xen/arch/arm/bootfdt.c
> index b6f92a174f5f..2673ad17a1e1 100644
> --- a/xen/arch/arm/bootfdt.c
> +++ b/xen/arch/arm/bootfdt.c
> @@ -225,7 +225,7 @@ static int __init process_reserved_memory_node(const void *fdt, int node,
> size_cells, data);
>
> if ( rc == -ENOSPC )
> - panic("Max number of supported reserved-memory regions reached.");
> + panic("Max number of supported reserved-memory regions reached.\n");
Trailing punctuation like . or ! is useless. Most messages don't have
them, and it just takes up space in .rodata, the console ring, and time
on the UART.
I'd recommend dropping the ones you modify, and/or cleaning it up more
widely.
~Andrew
next prev parent reply other threads:[~2023-06-14 8:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 7:30 [PATCH] xen: Append a newline character to panic() where missing Michal Orzel
2023-06-14 7:45 ` Luca Fancellu
2023-06-14 8:00 ` Jan Beulich
2023-06-14 8:04 ` Andrew Cooper [this message]
2023-06-14 8:09 ` Michal Orzel
2023-06-14 9:02 ` Julien Grall
2023-06-14 9:06 ` Michal Orzel
2023-06-14 9:09 ` Julien Grall
2023-06-15 20:53 ` Julien Grall
2023-06-14 9:51 ` Bertrand Marquis
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-all 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=261ab0b0-91ed-e6b7-730f-0ecb8a7b5635@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.