From: Jan Beulich <jbeulich@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: andrew.cooper3@citrix.com, bertrand.marquis@arm.com,
george.dunlap@citrix.com, julien@xen.org, michal.orzel@amd.com,
roger.pau@citrix.com, xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] docs/misra: document the expected sizes of integer types
Date: Fri, 15 Mar 2024 10:41:09 +0100 [thread overview]
Message-ID: <6a76723e-ba47-40b3-8f33-d68030b14299@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2403141516550.853156@ubuntu-linux-20-04-desktop>
On 14.03.2024 23:17, Stefano Stabellini wrote:
> Xen makes assumptions about the size of integer types on the various
> architectures. Document these assumptions.
My prior reservation wrt exact vs minimum sizes remains. Additionally,
is it really meaningful to document x86-32 as an architecture, when it's
been many years that the hypervisor cannot be built anymore for that
target? If it's not (just) the hypervisor build that's intended to be
covered here (the file living under docs/misra/, after all), can that
further purpose please be mentioned?
Jan
next prev parent reply other threads:[~2024-03-15 9:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 22:17 [PATCH v2] docs/misra: document the expected sizes of integer types Stefano Stabellini
2024-03-15 9:41 ` Jan Beulich [this message]
2024-03-16 0:07 ` Stefano Stabellini
2024-03-18 8:15 ` Jan Beulich
2024-03-19 3:37 ` Stefano Stabellini
2024-03-19 8:06 ` Jan Beulich
2024-03-20 6:01 ` Stefano Stabellini
2024-03-20 7:51 ` Jan Beulich
2024-03-21 1:46 ` Stefano Stabellini
2024-03-21 8:27 ` Jan Beulich
2024-03-21 19:03 ` Stefano Stabellini
2024-03-21 23:17 ` Julien Grall
2024-03-25 11:16 ` Jan Beulich
2024-03-25 11:17 ` Julien Grall
2024-04-02 1:50 ` Stefano Stabellini
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=6a76723e-ba47-40b3-8f33-d68030b14299@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=bertrand.marquis@arm.com \
--cc=george.dunlap@citrix.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.