From: Nicola Vetrini <nicola.vetrini@bugseng.com>
To: Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org, consulting@bugseng.com,
Simone Ballarin <simone.ballarin@bugseng.com>,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>,
"Daniel P. Smith" <dpsmith@apertussolutions.com>
Subject: Re: [XEN PATCH] automation/eclair_analysis: file exclusion automation
Date: Fri, 08 Dec 2023 10:56:57 +0100 [thread overview]
Message-ID: <554af5febdd5602d33ff420047d880cb@bugseng.com> (raw)
In-Reply-To: <2211ff2e-dd27-49a5-b41f-f56b60d2e3a5@xen.org>
On 2023-12-07 18:56, Julien Grall wrote:
> Hi Nicola,
>
> On 07/12/2023 17:53, Nicola Vetrini wrote:
>> On 2023-12-07 18:08, Julien Grall wrote:
>>> On 07/12/2023 11:39, Nicola Vetrini wrote:
>>>> +-doc_begin="libfdt is out of scope."
>>>> +-file_tag+={out_of_scope,"^xen/include/xen/libfdt/.*$"}
>>>
>>> AFAICT, before this was marked as "adopted". But this is now moved to
>>> "out_of_scope". Can you explain why?
>>>
>>> It also feels somewhat unrelated to the rest of the patch.
>>>
>>> Cheers,
>>
>> I mistakenly changed the tag. It is not unrelated, as it't not part of
>> exclude-list.json (perhaps unintentionally). The manual exclusions
>> that remain in out_of_scope.ecl are there for this reason, since I
>> wanted to keep the set of excluded files as it was before.
>
> Given that common/libfdt/* is part of the exclude-list.json, I can't
> see why include/xen/libfdt/* are not. So can you add it?
>
> Cheers,
Sure, I will.
--
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)
prev parent reply other threads:[~2023-12-08 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 11:39 [XEN PATCH] automation/eclair_analysis: file exclusion automation Nicola Vetrini
2023-12-07 17:08 ` Julien Grall
2023-12-07 17:53 ` Nicola Vetrini
2023-12-07 17:56 ` Julien Grall
2023-12-08 9:56 ` Nicola Vetrini [this message]
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=554af5febdd5602d33ff420047d880cb@bugseng.com \
--to=nicola.vetrini@bugseng.com \
--cc=cardoe@cardoe.com \
--cc=consulting@bugseng.com \
--cc=dpsmith@apertussolutions.com \
--cc=julien@xen.org \
--cc=simone.ballarin@bugseng.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.