From: Dmytro Prokopchuk1 <dmytro_prokopchuk1@epam.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Michal Orzel <michal.orzel@amd.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Resend: [PATCH v4 0/2] arm: address violations of MISRA C Rule 2.1
Date: Tue, 14 Oct 2025 16:37:10 +0000 [thread overview]
Message-ID: <9a3e591c-b94a-4dd4-9ab3-1e91ea155f5f@epam.com> (raw)
In-Reply-To: <cover.1759168391.git.dmytro_prokopchuk1@epam.com>
Hello,
looking forward to feedback, suggestions, or any required
changes to get this patch accepted.
BR, Dmytro.
On 9/29/25 21:43, Dmytro Prokopchuk1 wrote:
> This patch series consists of two patches that were received by dividing PATCH v3.
>
> Link to v3:
> https://patchew.org/Xen/620eb8fe22204e204cb471e93d2ea789f879d854.1758744144.git.dmytro._5Fprokopchuk1@epam.com/
>
> Changes in v4:
> - PATCH v3 was divided in two separate patches
> - added notes about predicates which end up as constants
>
> Test CI pipeline:
> https://gitlab.com/xen-project/people/dimaprkp4k/xen/-/pipelines/2070317153
>
> Dmytro Prokopchuk (2):
> arm/acpi: address violations of MISRA C Rule 2.1
> arm/gic_v3: address violations of MISRA C Rule 2.1
>
> xen/arch/arm/include/asm/domain_build.h | 9 ---------
> xen/arch/arm/include/asm/gic_v3_its.h | 11 ++---------
> 2 files changed, 2 insertions(+), 18 deletions(-)
>
prev parent reply other threads:[~2025-10-14 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 18:43 [PATCH v4 0/2] arm: address violations of MISRA C Rule 2.1 Dmytro Prokopchuk1
2025-09-29 18:43 ` [PATCH v4 1/2] arm/acpi: " Dmytro Prokopchuk1
2025-09-29 18:43 ` [PATCH v4 2/2] arm/gic_v3: " Dmytro Prokopchuk1
2025-10-14 16:37 ` Dmytro Prokopchuk1 [this message]
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=9a3e591c-b94a-4dd4-9ab3-1e91ea155f5f@epam.com \
--to=dmytro_prokopchuk1@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).