From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Simone Ballarin <simone.ballarin@bugseng.com>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
"Gianluca Luparini" <gianluca.luparini@bugseng.com>,
"Paul Durrant" <paul@xen.org>, "Wei Liu" <wl@xen.org>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: Re: [XEN PATCH v4 3/4] x86/viridian: address violations of MISRA C:2012 Rule 7.2
Date: Thu, 24 Aug 2023 12:34:58 +0200 [thread overview]
Message-ID: <fb8c98c3e0450dc5a30a02ea2e477865@bugseng.com> (raw)
In-Reply-To: <3007febabe8a13259dc10b566d23a27a89b75358.1690368810.git.simone.ballarin@bugseng.com>
On 26/07/2023 13:03, Simone Ballarin wrote:
> From: Gianluca Luparini <gianluca.luparini@bugseng.com>
>
> The xen sources contains violations of MISRA C:2012 Rule 7.2 whose
> headline states:
> "A 'u' or 'U' suffix shall be applied to all integer constants
> that are represented in an unsigned type".
>
> Add the 'U' suffix to integers literals with unsigned type and also to
> other
> literals used in the same contexts or near violations, when their
> positive
> nature is immediately clear. The latter changes are done for the sake
> of
> uniformity.
>
> Signed-off-by: Gianluca Luparini <gianluca.luparini@bugseng.com>
> Signed-off-by: Simone Ballarin <simone.ballarin@bugseng.com>
> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
> ---
> Changes in v4:
> - change commit headline
> - add Reviewed-by
>
> Changes in v3:
> - create this commit for 'viridian.c' and 'hyperv-tlfs.h'
> ---
> xen/arch/x86/hvm/viridian/viridian.c | 2 +-
> xen/arch/x86/include/asm/guest/hyperv-tlfs.h | 28 ++++++++++----------
> 2 files changed, 15 insertions(+), 15 deletions(-)
>
This patch has perhaps slipped by since its submission. As it can be
applied on top of
staging without conflicts, then it probably needs an ack from the x86
viridian maintainers.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-08-24 10:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-26 11:03 [XEN PATCH 0/4] xen: address violations of MISRA C:2012 Rule 7.2 Simone Ballarin
2023-07-26 11:03 ` [XEN PATCH v4 1/4] x86/vmx: " Simone Ballarin
2023-08-24 10:28 ` Nicola Vetrini
2023-08-24 22:04 ` Stefano Stabellini
2023-08-28 10:11 ` Simone Ballarin
2023-07-26 11:03 ` [XEN PATCH v4 2/4] xen/vpci: " Simone Ballarin
2023-08-24 10:40 ` Nicola Vetrini
2023-08-24 22:05 ` Need Ack, " Stefano Stabellini
2023-08-24 12:20 ` Roger Pau Monné
2023-08-24 22:05 ` Stefano Stabellini
2023-07-26 11:03 ` [XEN PATCH v4 3/4] x86/viridian: " Simone Ballarin
2023-08-24 10:34 ` Nicola Vetrini [this message]
2023-08-24 22:03 ` Need Ack, " Stefano Stabellini
2023-07-26 11:03 ` [XEN PATCH v4 4/4] xen/x86: " Simone Ballarin
2023-07-27 12:15 ` Jan Beulich
2023-07-26 12:02 ` [XEN PATCH 0/4] xen: " Jan Beulich
2023-07-26 12:33 ` Simone Ballarin
2023-08-09 8:58 ` Simone Ballarin
2023-08-09 9:15 ` Jan Beulich
2023-08-10 7:27 ` Simone Ballarin
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=fb8c98c3e0450dc5a30a02ea2e477865@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=gianluca.luparini@bugseng.com \
--cc=jbeulich@suse.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=simone.ballarin@bugseng.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.