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>,
"Simone Ballarin" <simone.ballarin@bugseng.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>
Subject: [XEN PATCH 0/3] x86: address violations of MISRA C Rule 16.3
Date: Wed, 6 Nov 2024 10:04:44 +0100 [thread overview]
Message-ID: <cover.1730880832.git.federico.serafini@bugseng.com> (raw)
Define pseudo keyword fallthrough for the x86 emulator,
use it and tag the rule as clean.
Federico Serafini (3):
x86/emul: define pseudo keyword fallthrough
x86/emul: use pseudo keyword fallthrough
automation/eclair: tag Rule 16.3 as clean
automation/eclair_analysis/ECLAIR/tagging.ecl | 3 ++-
xen/arch/x86/x86_emulate/decode.c | 6 ++++--
xen/arch/x86/x86_emulate/x86_emulate.c | 2 ++
xen/arch/x86/x86_emulate/x86_emulate.h | 10 ++++++++++
4 files changed, 18 insertions(+), 3 deletions(-)
--
2.43.0
next reply other threads:[~2024-11-06 9:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:04 Federico Serafini [this message]
2024-11-06 9:04 ` [XEN PATCH 1/3] x86/emul: define pseudo keyword fallthrough Federico Serafini
2024-11-06 11:22 ` Jan Beulich
2024-11-11 2:24 ` Stefano Stabellini
2024-11-11 6:34 ` Jan Beulich
2024-11-12 2:16 ` Stefano Stabellini
2024-11-12 9:35 ` Jan Beulich
2024-11-12 12:34 ` Federico Serafini
2024-11-06 9:04 ` [XEN PATCH 2/3] x86/emul: use " Federico Serafini
2024-11-06 11:28 ` Jan Beulich
2024-11-11 2:17 ` Stefano Stabellini
2024-11-06 9:04 ` [XEN PATCH 3/3] automation/eclair: tag Rule 16.3 as clean Federico Serafini
2024-11-11 2:17 ` Stefano Stabellini
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.1730880832.git.federico.serafini@bugseng.com \
--to=federico.serafini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=simone.ballarin@bugseng.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.