On 2026-01-20 13:09, Alejandro Vallejo wrote:
On Tue Jan 20, 2026 at 12:51 PM CET, Alejandro Vallejo wrote:
On Tue Jan 20, 2026 at 12:41 PM CET, Nicola Vetrini wrote:
On 2026-01-20 12:27, Alejandro Vallejo wrote:
On Tue Jan 20, 2026 at 12:21 PM CET, Nicola Vetrini wrote:
On 2026-01-20 10:38, Alejandro Vallejo wrote:
It's clean.
Signed-off-by: Alejandro Vallejo <[email protected]>
---
docs/misra/exclude-list.json | 4 ----
1 file changed, 4 deletions(-)
Hi. Do you have a link to a pipeline?
In the cover letter. I only run it on allcode.
I see. I can spot these additional violations from earlycpio.c. It
does
not result in a failure, but only because x86_64-allcode has also
other
non-clean guidelines and is thus allowed to fail. Ideally in some
copious free time I'd send a patch to create a subset of clean
guidelines for the *-allcode analysis that is failing, so that the
"allow_fail: true" can be removed.
https://eclair-analysis-logs.xenproject.org/fs/space/verdesse0/XEN.ecdf/xen-project/people/agvallejo/xen/ECLAIR_normal/ucode-disable_v4/X86_64/12771570090/PROJECT.ecd;/by_main_file/xen/lib/earlycpio.c.html
The web interface doesn't allow to search?! Sigh... thanks for the
pointer.
It's your usual mess of miscasting, enum-as-int, etc.
Would you rather keep the exclusion and deal with it later or let it
pile up?
I just don't have the time to go into it myself.
Well, including more stuff in the scan doesn't hurt and it's only a
handful of reports that could be fixed, but the maintainers will have
the final say. This file is not really inside my area as a reviewer, but
if it helps:
Reviewed-by: Nicola Vetrini <[email protected]>
--
Nicola Vetrini, B.Sc.
Software Engineer
BUGSENG (https://bugseng.com)
LinkedIn: https://www.linkedin.com/in/nicola-vetrini-a42471253
