From: Dmytro Prokopchuk1 <dmytro_prokopchuk1@epam.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Dmytro Prokopchuk1" <dmytro_prokopchuk1@epam.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Bertrand Marquis" <bertrand.marquis@arm.com>
Subject: [XEN PATCH 0/5] address violation of MISRA C Rule 5.5
Date: Fri, 4 Jul 2025 20:39:28 +0000 [thread overview]
Message-ID: <cover.1751659393.git.dmytro_prokopchuk1@epam.com> (raw)
This patch series fully eliminates MISRA C Rule 5.5
violations for ARM64.
The previous thread is here:
https://lore.kernel.org/xen-devel/48c7830931a98b2bf70ef1509f309b262b9e5792.1745427770.git.victorm.lira@amd.com/
where that violation was proposed to be deviated.
Dmytro Prokopchuk (5):
gnttab: address violation of MISRA C Rule 5.5
iommu: address violation of MISRA C Rule 5.5
x86/irq: address violation of MISRA C Rule 5.5
device-tree: address violation of MISRA C Rule 5.5
xen/bitops: address violation of MISRA C Rule 5.5
xen/arch/x86/irq.c | 2 +-
xen/common/device-tree/domain-build.c | 9 ++++-----
xen/common/grant_table.c | 22 +++++++++++++---------
xen/include/xen/bitops.h | 24 ++++++++++++------------
xen/include/xen/fdt-domain-build.h | 4 ++--
xen/include/xen/iommu.h | 5 ++---
xen/include/xen/irq.h | 4 ++--
7 files changed, 36 insertions(+), 34 deletions(-)
--
2.43.0
next reply other threads:[~2025-07-04 20:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 20:39 Dmytro Prokopchuk1 [this message]
2025-07-04 20:39 ` [XEN PATCH 1/5] gnttab: address violation of MISRA C Rule 5.5 Dmytro Prokopchuk1
2025-07-07 21:28 ` Stefano Stabellini
2025-07-04 20:39 ` [XEN PATCH 2/5] iommu: " Dmytro Prokopchuk1
2025-07-07 8:10 ` Jan Beulich
2025-07-07 21:21 ` Stefano Stabellini
2025-07-08 7:27 ` Jan Beulich
2025-07-04 20:39 ` [XEN PATCH 3/5] x86/irq: " Dmytro Prokopchuk1
2025-07-07 8:15 ` Jan Beulich
2025-07-07 21:25 ` Stefano Stabellini
2025-07-08 7:29 ` Jan Beulich
2025-07-04 20:39 ` [XEN PATCH 4/5] device-tree: " Dmytro Prokopchuk1
2025-07-07 21:29 ` Stefano Stabellini
2025-07-04 20:39 ` [XEN PATCH 5/5] xen/bitops: " Dmytro Prokopchuk1
2025-07-07 21:34 ` Stefano Stabellini
2025-07-04 21:12 ` [XEN PATCH 0/5] " Dmytro Prokopchuk1
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.1751659393.git.dmytro_prokopchuk1@epam.com \
--to=dmytro_prokopchuk1@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.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.