From: "Oleksii K." <oleksii.kurochko@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>,
xen-devel@lists.xenproject.org
Subject: Re: [XEN PATCH 0/4] address violations of MISRA C Rule 20.7
Date: Thu, 16 May 2024 17:58:19 +0200 [thread overview]
Message-ID: <7f8ef88d0a8bd3e40b213d19dfc80cd3fd2db298.camel@gmail.com> (raw)
In-Reply-To: <c67c1b8b-e14b-4c30-a381-1b89aedcddb9@suse.com>
On Wed, 2024-05-15 at 09:48 +0200, Jan Beulich wrote:
> Oleksii,
>
> On 15.05.2024 09:34, Nicola Vetrini wrote:
> > Hi all,
> >
> > this series aims to refactor some macros that cause violations of
> > MISRA C Rule
> > 20.7 ("Expressions resulting from the expansion of macro parameters
> > shall be
> > enclosed in parentheses"). All the macros touched by these patches
> > are in some
> > way involved in violations, and the strategy adopted to bring them
> > into
> > compliance is to add parentheses around macro arguments where
> > needed.
> >
> > Nicola Vetrini (4):
> > x86/vpmu: address violations of MISRA C Rule 20.7
> > x86/hvm: address violations of MISRA C Rule 20.7
> > x86_64/uaccess: address violations of MISRA C Rule 20.7
> > x86_64/cpu_idle: address violations of MISRA C Rule 20.7
>
> for 4.18 we took a relaxed approach towards (simple) changes for
> Misra purposes.
> I wonder whether you mean to permit the same for 4.19, or whether
> series like
> this one rather want/need delaying until after branching.
Lets follow the same approach for 4.19.
Sorry for delayed answer.
~ Oleksii
>
> Jan
>
> > xen/arch/x86/cpu/vpmu_amd.c | 4 ++--
> > xen/arch/x86/hvm/mtrr.c | 2 +-
> > xen/arch/x86/hvm/rtc.c | 2 +-
> > xen/arch/x86/include/asm/hvm/save.h | 2 +-
> > xen/arch/x86/include/asm/x86_64/uaccess.h | 7 ++++---
> > xen/arch/x86/x86_64/cpu_idle.c | 2 +-
> > 6 files changed, 10 insertions(+), 9 deletions(-)
> >
>
next prev parent reply other threads:[~2024-05-16 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 7:34 [XEN PATCH 0/4] address violations of MISRA C Rule 20.7 Nicola Vetrini
2024-05-15 7:34 ` [XEN PATCH 1/4] x86/vpmu: " Nicola Vetrini
2024-05-15 23:17 ` Stefano Stabellini
2024-05-21 11:20 ` Jan Beulich
2024-05-15 7:34 ` [XEN PATCH 2/4] x86/hvm: " Nicola Vetrini
2024-05-15 23:18 ` Stefano Stabellini
2024-05-16 7:06 ` Nicola Vetrini
2024-05-21 11:24 ` Jan Beulich
2024-05-15 7:34 ` [XEN PATCH 3/4] x86_64/uaccess: " Nicola Vetrini
2024-05-15 23:19 ` Stefano Stabellini
2024-05-21 11:27 ` Jan Beulich
2024-05-15 7:34 ` [XEN PATCH 4/4] x86_64/cpu_idle: " Nicola Vetrini
2024-05-15 23:19 ` Stefano Stabellini
2024-05-21 11:28 ` Jan Beulich
2024-05-15 7:48 ` [XEN PATCH 0/4] " Jan Beulich
2024-05-16 15:58 ` Oleksii K. [this message]
2024-05-16 16:08 ` Jan Beulich
2024-05-16 19:21 ` Oleksii K.
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=7f8ef88d0a8bd3e40b213d19dfc80cd3fd2db298.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=michal.orzel@amd.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger.pau@citrix.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.