From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: consulting@bugseng.com, Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org,
Luca Fancellu <Luca.Fancellu@arm.com>
Subject: Re: [XEN PATCH] xen: add acmacros.h to exclude-list.json
Date: Tue, 19 Dec 2023 11:51:33 +0100 [thread overview]
Message-ID: <2fd03776043811a8ceae9ae41de5f0fa@bugseng.com> (raw)
In-Reply-To: <055b6cf3-4f29-4f1d-b650-26c6d9be8832@suse.com>
On 2023-12-19 11:37, Jan Beulich wrote:
> On 19.12.2023 10:02, Nicola Vetrini wrote:
>> --- a/docs/misra/exclude-list.json
>> +++ b/docs/misra/exclude-list.json
>> @@ -209,6 +209,10 @@
>> "rel_path": "include/acpi/acglobal.h",
>> "comment": "Imported from Linux, ignore for now"
>> },
>> + {
>> + "rel_path": "include/acpi/acmacros.h",
>> + "comment": "Imported from Linux, ignore for now"
>> + },
>
> Together with what's already there (in context), wouldn't it better be
> the entire directory then which is excluded, or at least all
> include/acpi/ac*.h collectively (and perhaps also
> include/acpi/platform/ac*.h)?
>
> Jan
+Cc Luca Fancellu
Sure. I wasn't certain which files are imported from ACPI CA and which
aren't.
I'm also not sure whether "include/acpi/ac*.h" would be properly
recognized by other tooling that uses exclude-list.json (only cppcheck I
think). I Cc-ed Luca Fancellu on this.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
next prev parent reply other threads:[~2023-12-19 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 9:02 [XEN PATCH] xen: add acmacros.h to exclude-list.json Nicola Vetrini
2023-12-19 10:37 ` Jan Beulich
2023-12-19 10:51 ` Nicola Vetrini [this message]
2023-12-19 11:05 ` Nicola Vetrini
2023-12-19 11:09 ` Luca Fancellu
2023-12-20 0:17 ` Stefano Stabellini
2023-12-20 8:41 ` Jan Beulich
2023-12-20 8:50 ` Luca Fancellu
2023-12-20 9:10 ` Nicola Vetrini
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=2fd03776043811a8ceae9ae41de5f0fa@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=Luca.Fancellu@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=consulting@bugseng.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.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.