From: Federico Serafini <federico.serafini@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
"Federico Serafini" <federico.serafini@bugseng.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: [XEN PATCH v2 0/4] x86: address violations of MISRA C Rule 16.3
Date: Mon, 7 Oct 2024 16:16:15 +0200 [thread overview]
Message-ID: <cover.1728308312.git.federico.serafini@bugseng.com> (raw)
If these 4 patches will be committed, only 4 violations will be left:
these are under x86_emulate and involve some fallthrough cases.
I'll wait for instructions from x86 maintainers about the right "format" to make
the fallthrough intention explicit (i.e., a comment or the fallthrough keyword
that is not defined in x86-emulate.h at the moment).
Federico Serafini (4):
x86/emul: add defensive code
x86/emul: address violations of MISRA C Rule 16.3
xen/vpci: address violations of MISRA C Rule 16.3
xen/pci: address a violation of MISRA C Rule 16.3
xen/arch/x86/x86_emulate/fpu.c | 5 +++++
xen/arch/x86/x86_emulate/x86_emulate.c | 3 +++
xen/drivers/passthrough/pci.c | 4 +++-
xen/drivers/vpci/msix.c | 2 ++
4 files changed, 13 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2024-10-07 14:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:16 Federico Serafini [this message]
2024-10-07 14:16 ` [XEN PATCH v2 1/4] x86/emul: add defensive code Federico Serafini
2024-10-07 14:24 ` Jan Beulich
2024-10-07 14:16 ` [XEN PATCH v2 2/4] x86/emul: address violations of MISRA C Rule 16.3 Federico Serafini
2024-10-07 14:28 ` Jan Beulich
2024-10-07 14:16 ` [XEN PATCH v2 3/4] xen/vpci: " Federico Serafini
2024-10-07 21:44 ` Stefano Stabellini
2024-10-11 8:43 ` Roger Pau Monné
2024-10-07 14:16 ` [XEN PATCH v2 4/4] xen/pci: address a violation " Federico Serafini
2024-10-07 21:45 ` Stefano Stabellini
2024-10-11 8:45 ` Roger Pau Monné
2024-10-11 8:48 ` Jan Beulich
2024-10-11 9:03 ` Roger Pau Monné
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.1728308312.git.federico.serafini@bugseng.com \
--to=federico.serafini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.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.