From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Jan Beulich" <jbeulich@suse.com>,
sstabellini@kernel.org, consulting@bugseng.com,
"Doug Goldstein" <cardoe@cardoe.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH] xen: rework deviation to address varargs MISRA violations
Date: Mon, 05 Jan 2026 17:14:22 +0100 [thread overview]
Message-ID: <33ee7e20703de4f6b7a4c2d49dabece2@bugseng.com> (raw)
In-Reply-To: <cfaadea1-62a4-42b2-89ce-8b016ec030fe@citrix.com>
On 2026-01-05 15:58, Andrew Cooper wrote:
> On 05/01/2026 2:55 pm, Jan Beulich wrote:
>> On 31.12.2025 12:22, Nicola Vetrini wrote:
>>> --- a/xen/common/libelf/libelf-private.h
>>> +++ b/xen/common/libelf/libelf-private.h
>>> @@ -84,7 +84,9 @@
>>> #define elf_err(elf, fmt, args ... ) \
>>> elf_call_log_callback(elf, 1, fmt , ## args );
>>>
>>> -void elf_call_log_callback(struct elf_binary*, bool iserr, const
>>> char *fmt,...);
>>> +void
>>> +__attribute__ ((format (printf, 3, 4)))
>>> +elf_call_log_callback(struct elf_binary*, bool iserr, const char
>>> *fmt, ...);
>> Just one tiny, nit-like request here: If already you touch this, can
>> the
>> missing blank ahead of the first * please also be added at this
>> occasion?
>
> The parameter also needs a name. I have both fixed up locally.
>
> ~Andrew
Thanks
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
prev parent reply other threads:[~2026-01-05 16:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 11:22 [XEN PATCH] xen: rework deviation to address varargs MISRA violations Nicola Vetrini
2026-01-02 9:42 ` Andrew Cooper
2026-01-02 11:53 ` Nicola Vetrini
2026-01-05 11:54 ` Andrew Cooper
2026-01-05 16:05 ` Nicola Vetrini
2026-01-05 14:55 ` Jan Beulich
2026-01-05 14:58 ` Andrew Cooper
2026-01-05 16:14 ` Nicola Vetrini [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=33ee7e20703de4f6b7a4c2d49dabece2@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.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.