From: "Anthony PERARD" <anthony.perard@vates.tech>
To: "Jan Beulich" <jbeulich@suse.com>,
"Teddy Astie" <teddy.astie@vates.tech>
Cc: "Oleksii Kurochko" <oleksii.kurochko@gmail.com>,
"Community Manager" <community.manager@xenproject.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v8 2/2] xenpm: Add get-core-temp subcommand
Date: Wed, 11 Mar 2026 16:45:21 +0000 [thread overview]
Message-ID: <abGcHzCpY_Y7kq9r@l14> (raw)
In-Reply-To: <d7419a76-4c9a-4741-b738-9a4bdbfb0dd0@suse.com>
On Tue, Mar 03, 2026 at 12:54:28PM +0100, Jan Beulich wrote:
> On 03.03.2026 11:50, Teddy Astie wrote:
> > Le 02/03/2026 à 17:52, Jan Beulich a écrit :
> >> On 27.02.2026 18:00, Teddy Astie wrote:
> >>> + printf("No data\n");
> >>> + exit(ENODATA);
> >>
> >> In how far is using errno values as arguments to exit() a useful thing? (I
> >> think you had it like this before, and I merely forgot to ask.) Yes, I can
> >> see the tool using a number of exit(EINVAL), but I don't understand those
> >> either. This way you can't even document easily what particular exit codes
> >> mean, as the errno values may vary across OSes.
> >>
> >
> > I reused the exit(...) pattern used in xenpm, but I'm also fine by
> > returning simpler errors (like exit(1) or exit(EXIT_FAILURE)).
>
> Anthony, can you please suggest which one better fits the toolstack as a
> whole?
There isn't really one, but `exit(EXIT_FAILURE)` would be more
explicit.
--
Anthony Perard | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2026-03-11 16:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 17:00 [PATCH v8 1/2] libxc: Report consistent errors in xc_resource_op Teddy Astie
2026-02-27 17:00 ` [PATCH v8 2/2] xenpm: Add get-core-temp subcommand Teddy Astie
2026-03-02 16:50 ` Jan Beulich
2026-03-03 10:50 ` Teddy Astie
2026-03-03 11:54 ` Jan Beulich
2026-03-11 16:45 ` Anthony PERARD [this message]
2026-03-02 15:12 ` [PATCH v8 1/2] libxc: Report consistent errors in xc_resource_op Anthony PERARD
2026-03-03 10:36 ` Teddy Astie
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=abGcHzCpY_Y7kq9r@l14 \
--to=anthony.perard@vates.tech \
--cc=community.manager@xenproject.org \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=teddy.astie@vates.tech \
--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.