From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Michal Marek <michal.lkml@markovi.net>,
Rob Herring <robh+dt@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs
Date: Tue, 27 Sep 2022 10:10:18 -0500 [thread overview]
Message-ID: <20220927151018.GA1095814-robh@kernel.org> (raw)
In-Reply-To: <20220915114422.79378-1-dmitry.baryshkov@linaro.org>
On Thu, 15 Sep 2022 14:44:22 +0300, Dmitry Baryshkov wrote:
> It is useful to be able to recheck dtbs files against a limited set of
> DT schema files. This can be accomplished by using differnt
> DT_SCHEMA_FILES argument values while rerunning make dtbs_check. However
> for some reason if_changed_rule doesn't pick up the rule_dtc changes
> (and doesn't retrigger the build).
>
> Fix this by changing if_changed_rule to if_changed_dep and squashing DTC
> and dt-validate into a single new command. Then if_changed_dep triggers
> on DT_SCHEMA_FILES changes and reruns the build/check.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>
> Changes since v1:
> - Fixed the quiet_cmd_dtb to fit into the 7 chars limit
>
> ---
> scripts/Makefile.lib | 14 ++++++--------
> 1 file changed, 6 insertions(+), 8 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-09-27 15:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-15 11:44 [PATCH v2] kbuild: take into account DT_SCHEMA_FILES changes while checking dtbs Dmitry Baryshkov
2022-09-27 15:10 ` Rob Herring [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=20220927151018.GA1095814-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=robh+dt@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