From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, michal.orzel@amd.com,
xenia.ragiadakou@amd.com, ayan.kumar.halder@amd.com,
consulting@bugseng.com,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
"Paul Durrant" <paul@xen.org>,
"George Dunlap" <george.dunlap@citrix.com>,
"Julien Grall" <julien@xen.org>
Subject: [XEN PATCH v2 0/5] x86: address MISRA C:2012 Rule 5.3
Date: Tue, 8 Aug 2023 13:08:02 +0200 [thread overview]
Message-ID: <cover.1691492441.git.nicola.vetrini@bugseng.com> (raw)
This series addresses shadowing issues to resolve violations of Rule 5.3, whose
headline states:
"An identifier declared in an inner scope shall not hide an identifier
declared in an outer scope". To do this, suitable renames are made.
The thread of the first submission is here [1]
---
Changes in v2:
- Addressed numerous review comments
- Dropped patch 2/6 [2], as that has already been committed
[1] https://lists.xenproject.org/archives/html/xen-devel/2023-08/msg00538.html
[2] https://lists.xenproject.org/archives/html/xen-devel/2023-08/msg00539.html
Nicola Vetrini (5):
x86: address MISRA C:2012 Rule 5.3
xen/delay: address MISRA C:2012 Rule 5.3.
x86/include: address MISRA C:2012 Rule 5.3.
x86/xstate: address MISRA C:2012 Rule 5.3
x86: refactor macros in 'xen-mca.h'
xen/arch/x86/e820.c | 36 +++++++++----------
xen/arch/x86/guest/hyperv/hyperv.c | 4 +--
xen/arch/x86/guest/hypervisor.c | 2 +-
xen/arch/x86/guest/xen/xen.c | 4 +--
xen/arch/x86/include/asm/e820.h | 3 +-
xen/arch/x86/include/asm/guest/hypervisor.h | 2 +-
xen/arch/x86/include/asm/mpspec.h | 1 -
xen/arch/x86/include/asm/pv/shim.h | 2 +-
xen/arch/x86/pv/shim.c | 10 +++---
xen/arch/x86/setup.c | 8 ++---
xen/arch/x86/x86_64/mmconf-fam10h.c | 2 +-
xen/arch/x86/xstate.c | 30 ++++++++--------
xen/drivers/passthrough/amd/iommu_acpi.c | 2 +-
xen/include/public/arch-x86/xen-mca.h | 38 ++++++++++-----------
xen/include/xen/delay.h | 9 +++--
15 files changed, 78 insertions(+), 75 deletions(-)
--
2.34.1
next reply other threads:[~2023-08-08 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:08 Nicola Vetrini [this message]
2023-08-08 11:08 ` [XEN PATCH v2 1/5] x86: address MISRA C:2012 Rule 5.3 Nicola Vetrini
2023-08-08 13:46 ` Jan Beulich
2023-08-09 7:32 ` Nicola Vetrini
2023-08-08 11:08 ` [XEN PATCH v2 2/5] xen/delay: " Nicola Vetrini
2023-08-08 13:56 ` Jan Beulich
2023-08-08 13:57 ` Jan Beulich
2023-08-08 11:08 ` [XEN PATCH v2 3/5] x86/include: " Nicola Vetrini
2023-08-08 14:01 ` Jan Beulich
2023-08-08 11:08 ` [XEN PATCH v2 4/5] x86/xstate: " Nicola Vetrini
2023-08-08 14:03 ` Jan Beulich
2023-08-08 11:08 ` [XEN PATCH v2 5/5] x86: refactor macros in 'xen-mca.h' Nicola Vetrini
2023-08-08 12:02 ` Nicola Vetrini
2023-08-08 12:06 ` Jan Beulich
2023-08-08 14:46 ` Jan Beulich
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.1691492441.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.