From: dmkhn@proton.me
To: Jan Beulich <jbeulich@suse.com>
Cc: alejandro.garciavallejo@amd.com, andrew.cooper3@citrix.com,
anthony.perard@vates.tech, julien@xen.org, michal.orzel@amd.com,
roger.pau@citrix.com, sstabellini@kernel.org, dmukhin@ford.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v11 3/3] xen/domain: update create_dom0() messages
Date: Tue, 29 Jul 2025 23:54:36 +0000 [thread overview]
Message-ID: <aIlfOPUaPcmYKu2G@kraken> (raw)
In-Reply-To: <7fadf942-39ff-42b7-ba32-c37ad65fa5cc@suse.com>
On Tue, Jul 29, 2025 at 10:11:31AM +0200, Jan Beulich wrote:
> On 28.07.2025 20:34, dmkhn@proton.me wrote:
> > From: Denis Mukhin <dmukhin@ford.com>
> >
> > Use %pd for domain identification in error/panic messages in create_dom0().
>
> Except that ...
>
> > --- a/xen/arch/arm/domain_build.c
> > +++ b/xen/arch/arm/domain_build.c
> > @@ -2081,17 +2081,17 @@ void __init create_dom0(void)
> >
> > dom0 = domain_create(domid, &dom0_cfg, flags);
> > if ( IS_ERR(dom0) )
> > - panic("Error creating domain 0 (rc = %ld)\n", PTR_ERR(dom0));
> > + panic("Error creating d%d (rc = %ld)\n", domid, PTR_ERR(dom0));
>
> ... here you don't (and can't). To avoid people wondering when they later
Thanks for catching this! Will update.
> come across a commit, I think descriptions would better be accurate. It'll
> be Arm maintainers to judge whether they let you get away with this; as it
> covers x86 only anyway:
> Acked-by: Jan Beulich <jbeulich@suse.com>
Thanks!
>
> Jan
prev parent reply other threads:[~2025-07-29 23:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 18:34 [PATCH v11 0/3] xen/domain: domain ID allocation dmkhn
2025-07-28 18:34 ` [PATCH v11 1/3] xen/domain: unify " dmkhn
2025-07-29 10:34 ` Alejandro Vallejo
2025-07-29 23:53 ` dmkhn
2025-07-28 18:34 ` [PATCH v11 2/3] tools/tests: introduce unit tests for domain ID allocator dmkhn
2025-07-28 18:34 ` [PATCH v11 3/3] xen/domain: update create_dom0() messages dmkhn
2025-07-29 8:11 ` Jan Beulich
2025-07-29 23:54 ` dmkhn [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-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=aIlfOPUaPcmYKu2G@kraken \
--to=dmkhn@proton.me \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dmukhin@ford.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.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.