From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrejs Cainikovs <andrejs.cainikovs@toradex.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>
Subject: Re: Gitlab device tree check
Date: Wed, 18 Jan 2023 13:52:43 +0100 [thread overview]
Message-ID: <edb8437f-960f-632f-4829-cb612648dc44@linaro.org> (raw)
In-Reply-To: <ZRAP278MB0254511C101A8D3AFEF9324FE2C19@ZRAP278MB0254.CHEP278.PROD.OUTLOOK.COM>
On 16/01/2023 15:00, Andrejs Cainikovs wrote:
> Hi all,
>
> Right now I'm working on some extra checks for our Gitlab CI, and I'm a bit puzzled about how can I implement a nicely looking script that would execute "make CHECK_DTBS=y" on every touched device tree file. dts files are not a problem, but when it comes to .dtsi, which might be included in other .dtsi, makes the logic more complex than I would like to. I'm sure some of you might have a working solution for this scenario, and would appreciate if you could share your scripts/template. :)
You can touch files from commit and then make dtbs to get the list of
targets affected by DTSI.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-01-18 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 14:00 Gitlab device tree check Andrejs Cainikovs
2023-01-18 12:52 ` Krzysztof Kozlowski [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=edb8437f-960f-632f-4829-cb612648dc44@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrejs.cainikovs@toradex.com \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).