From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com, bertrand.marquis@arm.com, julien@xen.org,
Simone Ballarin <simone.ballarin@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
Julien Grall <jgrall@amazon.com>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH v2] automation/eclair_analysis: substitute deprecated service STD.emptrecd
Date: Fri, 19 Apr 2024 09:49:00 +0200 [thread overview]
Message-ID: <58ed38830469a027b9cedd9d5f68cfae@bugseng.com> (raw)
In-Reply-To: <c94d739e-0517-487f-8ba9-d9b19fe8f916@suse.com>
On 2024-04-19 09:35, Jan Beulich wrote:
> On 19.04.2024 09:16, Nicola Vetrini wrote:
>> The ECLAIR service STD.emptrecd is being deprecated; hence, as a
>> preventive
>> measure, STD.anonstct is used here, which for Xen's purposes has
>> equivalent
>> functionality.
>
> I'm sorry, but no, this still does not clarify things enough. It is
> still
> entirely unclear how "empty record" can reasonably be substituted by
> "anonymous struct". Even the expansion of the respective abbreviations
> continues to be just a guess.
>
> Jan
anonstct checks for structs with no named members, hence also empty
structs, but only the former is an undefined behaviour for C99.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2024-04-19 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 7:16 [XEN PATCH v2] automation/eclair_analysis: substitute deprecated service STD.emptrecd Nicola Vetrini
2024-04-19 7:35 ` Jan Beulich
2024-04-19 7:49 ` Nicola Vetrini [this message]
2024-04-19 9:21 ` Jan Beulich
2024-04-19 13:01 ` Nicola Vetrini
2024-04-19 14:26 ` Jan Beulich
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=58ed38830469a027b9cedd9d5f68cfae@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=simone.ballarin@bugseng.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/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.