From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, sstabellini@kernel.org,
michal.orzel@amd.com, xenia.ragiadakou@amd.com,
ayan.kumar.halder@amd.com, consulting@bugseng.com,
"George Dunlap" <george.dunlap@citrix.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Simone Ballarin" <simone.ballarin@bugseng.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Oleksii Kurochko" <oleksii.kurochko@gmail.com>
Subject: Re: [XEN PATCH 0/5] address violations of MISRA C rules
Date: Sat, 01 Jun 2024 19:19:53 +0200 [thread overview]
Message-ID: <fa17cb21b7bba2dabf49bba5138c1cf2@bugseng.com> (raw)
In-Reply-To: <b4267610-464b-479a-b886-12489c5e5a9b@citrix.com>
On 2024-06-01 16:37, Andrew Cooper wrote:
> On 01/06/2024 11:16 am, Nicola Vetrini wrote:
>> Patches 1 to 4 address violations of MISRA C Rule 20.12 by deviating
>> certain
>> uses of some macros, while the last patch addresses some regressions
>> introduced
>> by the latest bitops series
>>
>> Nicola Vetrini (5):
>> xen/domain: deviate violation of MISRA C Rule 20.12
>> x86/domain: deviate violation of MISRA C Rule 20.12
>> x86: deviate violation of MISRA C Rule 20.12
>> automation/eclair_analysis: address remaining violations of MISRA C
>> Rule 20.12
>> xen: fix MISRA regressions on rule 20.9 and 20.12
>
> I've committed patch 5 because it fixes a blocking failure in Gitlab CI
> from content already accepted for Xen 4.19.
>
Thanks
> The others look fine to me, but you'll need to negotiate with Oleksii
> (CC'd) to get them in, at this point in the release.
>
Well, having one more clean rule does look better for Xen, and the
changes to the codebase are harmless enough, but ultimately given the
closeness with the deadline I didn't really see a need to.
> Given that this series makes x86 clean to Rule 20.12, shouldn't there
> be
> a final patch making it blocking, to bring x86 in line with ARM?
>
Good point, I should have done that in patch 4. I'll do a follow-up
patch.
> ~Andrew
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2024-06-01 17:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 10:16 [XEN PATCH 0/5] address violations of MISRA C rules Nicola Vetrini
2024-06-01 10:16 ` [XEN PATCH 1/5] xen/domain: deviate violation of MISRA C Rule 20.12 Nicola Vetrini
2024-06-03 6:39 ` Jan Beulich
2024-06-03 13:21 ` Nicola Vetrini
2024-06-01 10:16 ` [XEN PATCH 2/5] x86/domain: " Nicola Vetrini
2024-06-04 5:58 ` Jan Beulich
2024-06-01 10:16 ` [XEN PATCH 3/5] x86: " Nicola Vetrini
2024-06-04 6:08 ` Jan Beulich
2024-06-07 14:34 ` Nicola Vetrini
2024-06-01 10:16 ` [XEN PATCH 4/5] automation/eclair_analysis: address remaining violations " Nicola Vetrini
2024-06-03 5:58 ` Jan Beulich
2024-06-03 7:13 ` Nicola Vetrini
2024-06-03 18:52 ` Jan Beulich
2024-06-03 19:12 ` Nicola Vetrini
2024-06-03 21:24 ` Jan Beulich
2024-06-03 21:37 ` Nicola Vetrini
2024-06-20 1:28 ` Stefano Stabellini
2024-06-01 10:16 ` [XEN PATCH 5/5] xen: fix MISRA regressions on rule 20.9 and 20.12 Nicola Vetrini
2024-06-01 12:47 ` Andrew Cooper
2024-06-01 12:58 ` Nicola Vetrini
2024-06-01 13:08 ` Andrew Cooper
2024-06-01 13:52 ` Nicola Vetrini
2024-06-01 14:01 ` Andrew Cooper
2024-06-01 14:37 ` [XEN PATCH 0/5] address violations of MISRA C rules Andrew Cooper
2024-06-01 17:19 ` Nicola Vetrini [this message]
2024-06-01 17:22 ` Andrew Cooper
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=fa17cb21b7bba2dabf49bba5138c1cf2@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=oleksii.kurochko@gmail.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.