From: Jan Beulich <jbeulich@suse.com>
To: Jason Andryuk <jason.andryuk@amd.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 4/6] libelf: Expand ELF note printing
Date: Wed, 27 Mar 2024 08:27:15 +0100 [thread overview]
Message-ID: <aa400a30-3f1f-4125-a759-d4e5825fea60@suse.com> (raw)
In-Reply-To: <20240326213847.3944-5-jason.andryuk@amd.com>
On 26.03.2024 22:38, Jason Andryuk wrote:
> @@ -145,13 +150,20 @@ elf_errorstatus elf_xen_parse_note(struct elf_binary *elf,
> elf_msg(elf, "ELF: note: %s = \"%s\"\n", note_desc[type].name, str);
> parms->elf_notes[type].type = XEN_ENT_STR;
> parms->elf_notes[type].data.str = str;
> - }
> - else
> - {
> + break;
> +
> + case ELFNOTE_INT:
> val = elf_note_numeric(elf, note);
> elf_msg(elf, "ELF: note: %s = %#" PRIx64 "\n", note_desc[type].name, val);
> parms->elf_notes[type].type = XEN_ENT_LONG;
> parms->elf_notes[type].data.num = val;
> + break;
> +
> + case ELFNOTE_NAME:
> + /* ELFNOTE_NAME has a newline printed at the end of the function to
> + * optionally allow printing customized details. */
> + elf_msg(elf, "ELF: note: %s", note_desc[type].name);
> + break;
Well. I said "brief comment" for several reasons. One of them being that
it would best fit on a single line. Since now it doesn't, I have to point
out that this way comment style is violated.
/* NB: Newline emitted further down. */
?
Jan
next prev parent reply other threads:[~2024-03-27 7:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 21:38 [PATCH v5 0/6] x86/pvh: Support relocating dom0 kernel Jason Andryuk
2024-03-26 21:38 ` [PATCH v5 1/6] Revert "xen/x86: bzImage parse kernel_alignment" Jason Andryuk
2024-03-27 7:22 ` Jan Beulich
2024-03-27 8:59 ` Roger Pau Monné
2024-03-27 14:08 ` Jason Andryuk
2024-03-27 14:19 ` Jan Beulich
2024-03-27 14:49 ` Jason Andryuk
2024-03-26 21:38 ` [PATCH v5 2/6] tools/init-xenstore-domain: Replace variable MB() usage Jason Andryuk
2024-03-26 21:38 ` [PATCH v5 3/6] tools: Move MB/GB() to common-macros.h Jason Andryuk
2024-03-26 21:38 ` [PATCH v5 4/6] libelf: Expand ELF note printing Jason Andryuk
2024-03-27 7:27 ` Jan Beulich [this message]
2024-03-26 21:38 ` [PATCH v5 5/6] xen/elfnote: Specify ELF Notes are x86-specific Jason Andryuk
2024-03-27 7:24 ` Jan Beulich
2024-03-26 21:38 ` [PATCH v5 6/6] x86/PVH: Support relocatable dom0 kernels Jason Andryuk
2024-03-26 21:47 ` [PATCH v5] RFC: x86/pvh: Make Xen PVH entrypoint PIC for x86-64 Jason Andryuk
2024-03-27 8:20 ` Jan Beulich
2024-03-27 14:15 ` Jason Andryuk
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=aa400a30-3f1f-4125-a759-d4e5825fea60@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=julien@xen.org \
--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.