From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Michal Orzel <michal.orzel@amd.com>, xen-devel@lists.xenproject.org
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien@xen.org>, Rahul Singh <rahul.singh@arm.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Bertrand Marquis <bertrand.marquis@arm.com>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH 0/2] Final series to make Arm MISRA allcode green
Date: Wed, 8 Apr 2026 10:22:14 +0100 [thread overview]
Message-ID: <68cea196-efdc-4481-9e4b-bb450bcd2071@citrix.com> (raw)
In-Reply-To: <20260407103434.90838-1-michal.orzel@amd.com>
On 07/04/2026 11:34 am, Michal Orzel wrote:
> No more regressions for clean guidelines:
> https://gitlab.com/xen-project/people/morzel/xen/-/pipelines/2433943072
>
> Michal Orzel (2):
> iommu/arm: smmu: Fix variable shadowing
> iommu/arm: ipmmu-vmsa: Fix variable shadowing
>
> xen/drivers/passthrough/arm/ipmmu-vmsa.c | 6 ++----
> xen/drivers/passthrough/arm/smmu.c | 7 +++----
> 2 files changed, 5 insertions(+), 8 deletions(-)
If all the violations are fixed, should this test be made blocking?
~Andrew
next prev parent reply other threads:[~2026-04-08 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 10:34 [PATCH 0/2] Final series to make Arm MISRA allcode green Michal Orzel
2026-04-07 10:34 ` [PATCH 1/2] iommu/arm: smmu: Fix variable shadowing Michal Orzel
2026-04-07 20:30 ` Stefano Stabellini
2026-04-07 10:34 ` [PATCH 2/2] iommu/arm: ipmmu-vmsa: " Michal Orzel
2026-04-07 13:48 ` Oleksandr Tyshchenko
2026-04-07 20:32 ` Stefano Stabellini
2026-04-08 9:22 ` Andrew Cooper [this message]
2026-04-08 9:46 ` [PATCH 0/2] Final series to make Arm MISRA allcode green Nicola Vetrini
2026-04-08 9:51 ` Andrew Cooper
2026-04-08 10:21 ` Nicola Vetrini
2026-04-08 10:36 ` Orzel, Michal
2026-04-08 10:42 ` Andrew Cooper
2026-04-08 11:01 ` Orzel, Michal
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=68cea196-efdc-4481-9e4b-bb450bcd2071@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=rahul.singh@arm.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.