From: Alessandro Zucchelli <alessandro.zucchelli@bugseng.com>
To: xen-devel@lists.xenproject.org
Cc: consulting@bugseng.com,
"Alessandro Zucchelli" <alessandro.zucchelli@bugseng.com>,
"Simone Ballarin" <simone.ballarin@bugseng.com>,
"Doug Goldstein" <cardoe@cardoe.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>
Subject: [PATCH 0/2] automation/eclair_analysis: deviate MISRA C Rule 21.2
Date: Wed, 19 Jun 2024 19:09:08 +0200 [thread overview]
Message-ID: <cover.1718816397.git.alessandro.zucchelli@bugseng.com> (raw)
This series aims to address several violations of Rule 21.2 which states the
following: A reserved identifier or reserved macro name shall not be declared.
The series contains two patches, one changes x86/APIC which used an identifier
starting with '__', the second deviates all reserved identifiers with the
exception of those starting with "__builtin_" which still remain available.
Alessandro Zucchelli (1):
automation/eclair_analysis: deviate MISRA C Rule 21.2
Nicola Vetrini (1):
x86/APIC: address violation of MISRA C Rule 21.2
automation/eclair_analysis/ECLAIR/deviations.ecl | 11 +++++++++++
xen/arch/x86/apic.c | 4 ++--
2 files changed, 13 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-19 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 17:09 Alessandro Zucchelli [this message]
2024-06-19 17:09 ` [PATCH 1/2] automation/eclair_analysis: deviate MISRA C Rule 21.2 Alessandro Zucchelli
2024-06-20 9:11 ` Jan Beulich
2024-06-21 1:02 ` Stefano Stabellini
2024-06-21 6:17 ` Jan Beulich
2024-06-21 23:27 ` Stefano Stabellini
2024-06-24 7:31 ` Jan Beulich
2024-06-19 17:09 ` [PATCH 2/2] x86/APIC: address violation of " Alessandro Zucchelli
2024-06-20 9:15 ` 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.1718816397.git.alessandro.zucchelli@bugseng.com \
--to=alessandro.zucchelli@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.