From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: nicola.vetrini@bugseng.com, xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com,
"Simone Ballarin" <simone.ballarin@bugseng.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"George Dunlap" <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [XEN PATCH 0/6] address several violations of MISRA Rule 20.7
Date: Tue, 11 Jun 2024 17:53:30 +0200 [thread overview]
Message-ID: <cover.1718117557.git.nicola.vetrini@bugseng.com> (raw)
Hi all,
this series addresses several violations of Rule 20.7, as well as a
small fix to the ECLAIR integration scripts that do not influence
the current behaviour, but were mistakenly part of the upstream
configuration.
Note that by applying this series the rule has a few leftover violations.
Most of those are in x86 code in xen/arch/x86/include/asm/msi.h .
I did send a patch [1] to deal with those, limited only to addressing the MISRA
violations, but in the end it was dropped in favour of a more general cleanup of
the file upon agreement, so this is why those changes are not included here.
[1] https://lore.kernel.org/xen-devel/2f2c865f20d0296e623f1d65bed25c083f5dd497.1711700095.git.nicola.vetrini@bugseng.com/
Nicola Vetrini (6):
automation/eclair: address violations of MISRA C Rule 20.7
xen/self-tests: address violations of MISRA rule 20.7
xen/guest_access: address violations of MISRA rule 20.7
x86emul: address violations of MISRA C Rule 20.7
x86/irq: address violations of MISRA C Rule 20.7
automation/eclair_analysis: clean ECLAIR configuration scripts
automation/eclair_analysis/ECLAIR/analyze.sh | 3 +--
automation/eclair_analysis/ECLAIR/deviations.ecl | 8 ++++++++
xen/arch/x86/x86_emulate/x86_emulate.c | 4 ++--
xen/include/xen/guest_access.h | 4 ++--
xen/include/xen/irq.h | 2 +-
xen/include/xen/self-tests.h | 8 ++++----
6 files changed, 18 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-11 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 15:53 Nicola Vetrini [this message]
2024-06-11 15:53 ` [XEN PATCH 1/6] automation/eclair: address violations of MISRA C Rule 20.7 Nicola Vetrini
2024-06-11 15:53 ` [XEN PATCH 2/6] xen/self-tests: address violations of MISRA rule 20.7 Nicola Vetrini
2024-06-12 9:12 ` Jan Beulich
2024-06-11 15:53 ` [XEN PATCH 3/6] xen/guest_access: " Nicola Vetrini
2024-06-12 9:13 ` Jan Beulich
2024-06-11 15:53 ` [XEN PATCH 4/6] x86emul: address violations of MISRA C Rule 20.7 Nicola Vetrini
2024-06-12 9:19 ` Jan Beulich
2024-06-12 9:52 ` Nicola Vetrini
2024-06-12 10:36 ` Jan Beulich
2024-06-13 9:41 ` Nicola Vetrini
2024-06-11 15:53 ` [XEN PATCH 5/6] x86/irq: " Nicola Vetrini
2024-06-12 9:22 ` Jan Beulich
2024-06-11 15:53 ` [XEN PATCH 6/6] automation/eclair_analysis: clean ECLAIR configuration scripts 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.1718117557.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.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.