From: Jan Beulich <jbeulich@suse.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Andrew Cooper" <andrew.cooper3@citrix.com>,
"Teddy Astie" <teddy.astie@vates.tech>,
"Roger Pau Monné" <roger@xenproject.org>,
"Nicola Vetrini" <nicola.vetrini@bugseng.com>
Subject: [PATCH 0/6] x86: address remaining rule 18.2 violations and mark clean
Date: Wed, 9 Sep 2026 14:57:49 +0200 [thread overview]
Message-ID: <c3614ea0-e5b3-4cfd-820b-9320ac327292@suse.com> (raw)
Arm64 is already clean. And all four analysis jobs have already been clean
for rule 18.1.
1: PV: adjust APPEND_CALL() to comply to Misra rule 18.2
2: alternatives: adjust _apply_alternatives() to comply to Misra rule 18.2
3: EFI: adjust efi_multiboot2_prelude() to comply to Misra rule 18.2
4: cpufreq: annotate Eclair false-positives for rule 18.2
5: Viridian: annotate Eclair false-positives for rule 18.2
6: automation/Eclair: tag rules 18.1 and 18.2 as clean
https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/2832933871
Jan
next reply other threads:[~2026-09-09 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 12:57 Jan Beulich [this message]
2026-09-09 12:59 ` [PATCH 1/6] x86/PV: adjust APPEND_CALL() to comply to Misra rule 18.2 Jan Beulich
2026-09-09 12:59 ` [PATCH 2/6] x86/alternatives: adjust _apply_alternatives() " Jan Beulich
2026-09-09 13:00 ` [PATCH 3/6] x86/EFI: adjust efi_multiboot2_prelude() " Jan Beulich
2026-09-09 13:54 ` Marek Marczykowski
2026-09-09 13:00 ` [PATCH 4/6] x86/cpufreq: annotate Eclair false-positives for " Jan Beulich
2026-09-09 13:01 ` [PATCH 5/6] x86/Viridian: " Jan Beulich
2026-09-09 13:13 ` Nicola Vetrini
2026-09-09 13:01 ` [PATCH 6/6] automation/Eclair: tag rules 18.1 and 18.2 as clean 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=c3614ea0-e5b3-4cfd-820b-9320ac327292@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=nicola.vetrini@bugseng.com \
--cc=roger@xenproject.org \
--cc=teddy.astie@vates.tech \
--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.