From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Rob Herring (Arm)" <robh@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Dinh Nguyen <dinguyen@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: dts: socfpga: Add basic support for Terrasic's de10-nano
Date: Fri, 31 Jan 2025 22:30:21 +0100 [thread overview]
Message-ID: <582275fe-4c0d-46b8-8fb6-3f977b275da0@kernel.org> (raw)
In-Reply-To: <3101a214-1498-4671-9062-89d2f9d8369b@kernel.org>
On 31/01/2025 22:28, Krzysztof Kozlowski wrote:
> On 31/01/2025 17:47, Uwe Kleine-König wrote:
>>> Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
>>> are fixed by another series. Ultimately, it is up to the platform
>>> maintainer whether these warnings are acceptable or not. No need to reply
>>> unless the platform maintainer has comments.
>>>
>>> If you already ran DT checks and didn't see these error(s), then
>>> make sure dt-schema is up to date:
>>>
>>> pip3 install dtschema --upgrade
>>>
>>>
>>> New warnings running 'make CHECK_DTBS=y for arch/arm/boot/dts/intel/' for 20250130074553.92023-2-u.kleine-koenig@baylibre.com:
>>
>> Maybe I can learn something here: Is there a command that only checks
>> this single dtb file?
>>
>
> You asked about this and I gave you the link to blog describing this twice.
Actually only once at v2. I thought I mentioned testing on v1, but
apparently not.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-31 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 7:45 [PATCH v2] ARM: dts: socfpga: Add basic support for Terrasic's de10-nano Uwe Kleine-König
2025-01-30 8:46 ` Krzysztof Kozlowski
2025-01-30 12:59 ` Andrew Lunn
2025-01-30 23:38 ` Rob Herring (Arm)
2025-01-31 16:47 ` Uwe Kleine-König
2025-01-31 21:28 ` Krzysztof Kozlowski
2025-01-31 21:30 ` Krzysztof Kozlowski [this message]
2025-02-03 11:39 ` Uwe Kleine-König
-- strict thread matches above, loose matches on Subject: below --
2025-02-05 9:22 kernel test robot
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=582275fe-4c0d-46b8-8fb6-3f977b275da0@kernel.org \
--to=krzk@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robh@kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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.