From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nikolaos Pasaloukos <nikolaos.pasaloukos@blaize.com>,
"robh@kernel.org" <robh@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"will@kernel.org" <will@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"olof@lixom.net" <olof@lixom.net>,
Neil Jones <neil.jones@blaize.com>,
Matt Redfearn <matthew.redfearn@blaize.com>,
James Cowgill <james.cowgill@blaize.com>,
"heiko.stuebner@cherry.de" <heiko.stuebner@cherry.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"macromorgan@hotmail.com" <macromorgan@hotmail.com>,
"sre@kernel.org" <sre@kernel.org>,
"hvilleneuve@dimonoff.com" <hvilleneuve@dimonoff.com>,
"andre.przywara@arm.com" <andre.przywara@arm.com>,
"rafal@milecki.pl" <rafal@milecki.pl>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"andersson@kernel.org" <andersson@kernel.org>,
"konrad.dybcio@linaro.org" <konrad.dybcio@linaro.org>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"neil.armstrong@linaro.org" <neil.armstrong@linaro.org>,
"m.szyprowski@samsung.com" <m.szyprowski@samsung.com>,
"nfraprado@collabora.com" <nfraprado@collabora.com>,
"u-kumar1@ti.com" <u-kumar1@ti.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 4/5] arm64: Add initial support for Blaize BLZP1600 CB2
Date: Thu, 25 Apr 2024 13:09:17 +0200 [thread overview]
Message-ID: <57698077-d09d-4ada-90a3-69ddd10bbb55@linaro.org> (raw)
In-Reply-To: <a5282012-d38c-4a02-9292-8eab156ddb98@blaize.com>
On 25/04/2024 12:41, Nikolaos Pasaloukos wrote:
>>> +
>>> + soc {
>>
>> This does not cause dtbs_check W=1 warnings? Surprising a bit... This
>> should cause big fat warning, so I have doubts patchset was tested.
>>
>>
>> Best regards,
>> Krzysztof
>>
>
> No it doesn't cause any warnings. I did:
> make arch=arm64 dt_binding_check
> make arch=arm64 dtbs_check W=1
> I don't get any warnings. Could you please let me know what kind of
> warning I should get? Am I doing something wrong and I don't get
> the warning?
I was expecting one for missing soc unit address, but you are right -
your ranges are empty, so "soc" is ok. I keep forgetting that
distinction. Looks fine then.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-04-25 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 9:15 [PATCH v3 0/5] Add support for Blaize BLZP1600 SoC Niko Pasaloukos
2024-04-25 9:15 ` [PATCH v3 1/5] dt-bindings: Add Blaize vendor prefix Niko Pasaloukos
2024-04-25 16:33 ` Rob Herring
2024-04-25 9:15 ` [PATCH v3 2/5] dt-bindings: arm: blaize: Add Blaize BLZP1600 SoC Niko Pasaloukos
2024-04-25 9:16 ` Krzysztof Kozlowski
2024-04-25 9:20 ` Nikolaos Pasaloukos
2024-04-25 9:15 ` [PATCH v3 3/5] arm64: Add Blaize BLZP1600 SoC family Niko Pasaloukos
2024-04-25 9:15 ` [PATCH v3 4/5] arm64: Add initial support for Blaize BLZP1600 CB2 Niko Pasaloukos
2024-04-25 9:21 ` Krzysztof Kozlowski
2024-04-25 10:41 ` Nikolaos Pasaloukos
2024-04-25 11:09 ` Krzysztof Kozlowski [this message]
2024-04-25 16:56 ` Rob Herring
2024-04-25 9:15 ` [PATCH v3 5/5] arm64: defconfig: Enable ARCH_BLAIZE_BLZP1600 Niko Pasaloukos
2024-04-25 16:08 ` [PATCH v3 0/5] Add support for Blaize BLZP1600 SoC Conor Dooley
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=57698077-d09d-4ada-90a3-69ddd10bbb55@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=andre.przywara@arm.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=heiko.stuebner@cherry.de \
--cc=hvilleneuve@dimonoff.com \
--cc=james.cowgill@blaize.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=macromorgan@hotmail.com \
--cc=matthew.redfearn@blaize.com \
--cc=neil.armstrong@linaro.org \
--cc=neil.jones@blaize.com \
--cc=nfraprado@collabora.com \
--cc=nikolaos.pasaloukos@blaize.com \
--cc=olof@lixom.net \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=u-kumar1@ti.com \
--cc=will@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