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, jbeulich@suse.com,
andrew.cooper3@citrix.com, roger.pau@citrix.com,
Nicola Vetrini <nicola.vetrini@bugseng.com>,
Simone Ballarin <simone.ballarin@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>, Wei Liu <wl@xen.org>
Subject: [XEN PATCH][for-4.19 0/2] address violations of MISRA C:2012 Rule 11.9
Date: Thu, 5 Oct 2023 10:45:18 +0200 [thread overview]
Message-ID: <cover.1696494834.git.nicola.vetrini@bugseng.com> (raw)
Rule 11.9 forbids the usage of '0' as a null pointer constant, therefore uses of
this pattern have been amended. One exception, recorded in rules.rst, is in
__ACCESS_ONCE to do a scalar type check.
The series only touches common headers, therefore it should be safe to include
in the for-4.19 branch.
Nicola Vetrini (2):
xen: introduce a deviation for Rule 11.9
xen/spinlock: fix use of 0 as a null pointer constant
.../eclair_analysis/ECLAIR/deviations.ecl | 23 +++++++------------
docs/misra/rules.rst | 3 ++-
xen/include/xen/compiler.h | 5 +++-
xen/include/xen/kernel.h | 2 +-
xen/include/xen/spinlock.h | 2 +-
5 files changed, 16 insertions(+), 19 deletions(-)
--
2.34.1
next reply other threads:[~2023-10-05 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 8:45 Nicola Vetrini [this message]
2023-10-05 8:45 ` [XEN PATCH][for-4.19 1/2] xen: introduce a deviation for Rule 11.9 Nicola Vetrini
2023-10-06 1:06 ` Stefano Stabellini
2023-10-06 9:27 ` Julien Grall
2023-10-06 9:58 ` Nicola Vetrini
2023-10-06 12:33 ` Julien Grall
2023-10-07 0:33 ` Stefano Stabellini
2023-10-10 9:54 ` Nicola Vetrini
2023-10-05 8:45 ` [XEN PATCH][for-4.19 2/2] xen/spinlock: fix use of 0 as a null pointer constant Nicola Vetrini
2023-10-06 1:07 ` Stefano Stabellini
2023-10-06 19:16 ` andrew.cooper3
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.1696494834.git.nicola.vetrini@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=andrew.cooper3@citrix.com \
--cc=ayan.kumar.halder@amd.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=simone.ballarin@bugseng.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.