From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Alejandro Vallejo" <alejandro.garciavallejo@amd.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v5 2/2] earlycpio: lib-ify earlycpio.c
Date: Thu, 22 Jan 2026 15:18:35 +0100 [thread overview]
Message-ID: <02004b6ee5ddb57f4b834163a955d29b@bugseng.com> (raw)
In-Reply-To: <947a4230-4a1e-4178-b7f0-ae5618f4303d@citrix.com>
On 2026-01-22 13:50, Andrew Cooper wrote:
> On 22/01/2026 8:27 am, Jan Beulich wrote:
>> On 21.01.2026 16:47, Alejandro Vallejo wrote:
>>> --- a/docs/misra/exclude-list.json
>>> +++ b/docs/misra/exclude-list.json
>>> @@ -121,10 +121,6 @@
>>> "rel_path": "common/bunzip2.c",
>>> "comment": "Imported from Linux, ignore for now"
>>> },
>>> - {
>>> - "rel_path": "common/earlycpio.c",
>>> - "comment": "Imported from Linux, ignore for now"
>>> - },
>>> {
>>> "rel_path": "common/gzip/*",
>>> "comment": "Imported from Linux, ignore for now"
>> Judging from Andrew's
>> https://gitlab.com/xen-project/hardware/xen-staging/-/pipelines/2277362625
>> this doesn't quite work. As I had expected, since the file is compiled
>> unconditionally now in its new location, some violations are now also
>> unconditionally reported. (Some, checked for at linking time only, may
>> not
>> be reported anymore for the *-amd analysis jobs.)
>
> Yeah, in hindsight this seems obvious, given that we're compiling then
> discarding.
>
> There are two options:
>
> 1. Use an earlier form which adds the new location to the exclude list
> (Still needs to be in this patch for bisectibility.)
> 2. Fix up the violations first (only 6 in total)
>
> Two of the violations look easy to fix, two need the deviation for
> octal
> numbers, but two essentially-char violations look to be hard. The
> logic
> is doing ASCII manipulation in what I would consider to be the
> appropriate/canonical way, but Eclair does not like the mixture of ints
> and character literals.
>
> I dislike option 1, but as (contrary to my expectations) this is
> interfering with the *-amd build, I'll tolerate it.
>
I agree that Solution 1 is the easiest to implement. An alternative
could be to fix the regressions for R7.1 and R20.7 (they're trivial)
regardless and add casts to sidestep MISRA for R10.2.
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
next prev parent reply other threads:[~2026-01-22 14:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:47 [PATCH v5 0/2] Alejandro Vallejo
2026-01-21 15:47 ` [PATCH v5 1/2] xen: Allow lib-y targets to also be .init.o Alejandro Vallejo
2026-01-22 9:49 ` Jan Beulich
2026-01-22 10:01 ` Jan Beulich
2026-01-22 11:02 ` Alejandro Vallejo
2026-01-22 11:04 ` Jan Beulich
2026-01-22 12:12 ` Alejandro Vallejo
2026-01-23 10:56 ` Orzel, Michal
2026-01-23 11:37 ` Jan Beulich
2026-01-23 12:53 ` Orzel, Michal
2026-01-21 15:47 ` [PATCH v5 2/2] earlycpio: lib-ify earlycpio.c Alejandro Vallejo
2026-01-21 19:37 ` Andrew Cooper
2026-01-22 8:27 ` Jan Beulich
2026-01-22 12:50 ` Andrew Cooper
2026-01-22 14:18 ` Nicola Vetrini [this message]
2026-01-22 17:48 ` Alejandro Vallejo
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=02004b6ee5ddb57f4b834163a955d29b@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=alejandro.garciavallejo@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.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.