From: Krzysztof Kozlowski <krzk@kernel.org>
To: Philip Oberfichtner <pro@denx.de>, devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Winker Matthias <Matthias.Winker@de.bosch.com>
Subject: Re: [PATCH 2/2] arm: dts: Add device tree for bosch acc board
Date: Thu, 21 Apr 2022 09:37:35 +0200 [thread overview]
Message-ID: <af9a8506-7c8e-d76c-c14f-1bf1c913a18c@kernel.org> (raw)
In-Reply-To: <cd7546a341d475eca99a446b6c8a5141056b3bc8.camel@denx.de>
On 21/04/2022 09:06, Philip Oberfichtner wrote:
>
> The "operating-points" and "fsl,soc-operating-points" properties are
> defined in imx6q.dtsi. We are just overwriting them here.
OK, thanks for explanation.
(...)
>> Please run `make dtbs_check` (see Docs for this) and fix the
>> warnings.
>> Please fix automated check warnings before using reviewers time.
>
> I built with W=1 and used checkpatch.pl. But I'm having trouble using
> make dtbs_check. Seems like I get all warnings for all possible dts. Is
> there a way to get warnings for a single dt only?
I think no, it is not possible at the moment. I understand it's a pain
and already someone proposed to have a ability to check only subset of
DTS files.
Workaround is to build imx defconfig, run dtbs_check, touch your files
and run dtbs_check again looking for results.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-21 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 10:19 [PATCH 0/2] arm: dts: Add device tree for bosch acc board Philip Oberfichtner
2022-04-12 10:19 ` [PATCH 1/2] dt-bindings: arm: Add " Philip Oberfichtner
2022-04-12 11:00 ` Krzysztof Kozlowski
2022-04-12 10:19 ` [PATCH 2/2] arm: dts: Add device tree for " Philip Oberfichtner
2022-04-12 11:10 ` Krzysztof Kozlowski
2022-04-21 7:06 ` Philip Oberfichtner
2022-04-21 7:37 ` Krzysztof Kozlowski [this message]
2022-04-12 11:11 ` Krzysztof Kozlowski
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=af9a8506-7c8e-d76c-c14f-1bf1c913a18c@kernel.org \
--to=krzk@kernel.org \
--cc=Matthias.Winker@de.bosch.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pro@denx.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).