From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: michal.orzel@amd.com, xenia.ragiadakou@amd.com,
ayan.kumar.halder@amd.com, consulting@bugseng.com,
Nicola Vetrini <nicola.vetrini@bugseng.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Rahul Singh <rahul.singh@arm.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Jan Beulich <jbeulich@suse.com>, Wei Liu <wl@xen.org>
Subject: [XEN PATCH v2 0/3] fix violations of MISRA C:2012 Rule 3.1
Date: Mon, 19 Jun 2023 11:56:10 +0200 [thread overview]
Message-ID: <cover.1687167502.git.nicola.vetrini@bugseng.com> (raw)
Hi all,
This patch series is about the violations present in the Xen sources of
Rule 3.1 from MISRA C:2012, whose headline states:
"The character sequences '/*' and '//' shall not be used within a comment".
In the context of the effort to bring xen into compliance w.r.t.
MISRA C:2012, and Rule 3.1 being already approved for the project (as
evidenced by `docs/misra/rules.rst'), these violations need to be fixed.
Most of the violations are due to the presence of links to webpages within
C-style comment blocks, such as:
xen/arch/arm/include/asm/smccc.h:37.1-41.3
/*
* This file provides common defines for ARM SMC Calling Convention as
* specified in
* http://infocenter.arm.com/help/topic/com.arm.doc.den0028a/index.html
*/
In this case, I propose to deviate all of these occurrences with a
project deviation to be captured by a tool configuration
(not included in any patch from this series).
There are, however, a few other violations that do not fall under this
category, which are the focus of the following set of patches. They either:
1. remove the nested '//' character sequence within a block comment;
2. remove the surrounding comment.
Thanks,
Nicola
Nicola Vetrini (3):
xen/arch/arm: fix violations of MISRA C:2012 Rule 3.1
xen/drivers/passthrough/arm/smmu-v3.c: fix violations of MISRA C:2012
Rule 3.1
xen: fix violations of MISRA C:2012 Rule 3.1
xen/arch/arm/include/asm/arm32/flushtlb.h | 8 ++++----
xen/arch/arm/include/asm/arm64/flushtlb.h | 8 ++++----
xen/common/xmalloc_tlsf.c | 3 ---
xen/drivers/passthrough/arm/smmu-v3.c | 4 ++--
xen/include/xen/atomic.h | 2 +-
5 files changed, 11 insertions(+), 14 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-19 9:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 9:56 Nicola Vetrini [this message]
2023-06-19 9:56 ` [XEN PATCH v2 1/3] xen/arch/arm: fix violations of MISRA C:2012 Rule 3.1 Nicola Vetrini
2023-06-19 10:01 ` Julien Grall
2023-06-19 10:25 ` Jan Beulich
2023-06-19 10:29 ` Julien Grall
2023-06-20 13:56 ` Nicola Vetrini
2023-06-19 9:56 ` [XEN PATCH v2 2/3] xen/drivers/passthrough/arm/smmu-v3.c: " Nicola Vetrini
2023-06-19 10:10 ` Julien Grall
2023-06-20 8:06 ` Nicola Vetrini
2023-06-19 9:56 ` [XEN PATCH v2 3/3] xen: " Nicola Vetrini
2023-06-19 10:29 ` Jan Beulich
2023-06-20 8:00 ` Nicola Vetrini
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=cover.1687167502.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=rahul.singh@arm.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.