mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: "Peter Griffin" <peter.griffin@linaro.org>,
	devicetree@vger.kernel.org,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	"André Draszik" <andre.draszik@linaro.org>,
	"Alim Akhtar" <alim.akhtar@samsung.com>,
	"Conor Dooley" <conor+dt@kernel.org>,
	linux-samsung-soc@vger.kernel.org,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	"Sam Protsenko" <semen.protsenko@linaro.org>
Subject: Re: [PATCH v1] arm64: dts: exynos: update all samsung,mode constants
Date: Sat, 15 Feb 2025 15:52:14 +0200	[thread overview]
Message-ID: <8bcf7557-dff3-4017-84b1-184b20e028bf@gmail.com> (raw)
In-Reply-To: <173920411901.476943.11749535762195189252.robh@kernel.org>

On 2/10/25 18:22, Rob Herring (Arm) wrote:
> On Sun, 09 Feb 2025 15:20:43 +0200, Ivaylo Ivanov wrote:
>> Update all samsung,mode property values to account for renaming USI_V2
>> constants to USI_MODE in the bindings.
>>
>> Signed-off-by: Ivaylo Ivanov <ivo.ivanov.ivanov1@gmail.com>
>> ---
>> Patch picked from [1] and rebased on linux-next
>>
>> [1] https://lore.kernel.org/all/20250204172803.3425496-1-ivo.ivanov.ivanov1@gmail.com/
>> ---
>>  arch/arm64/boot/dts/exynos/exynos850.dtsi     | 14 +++---
>>  arch/arm64/boot/dts/exynos/exynosautov9.dtsi  | 48 +++++++++----------
>>  .../arm64/boot/dts/exynos/exynosautov920.dtsi |  2 +-
>>  .../dts/exynos/google/gs101-pixel-common.dtsi |  4 +-
>>  arch/arm64/boot/dts/exynos/google/gs101.dtsi  |  2 +-
>>  5 files changed, 35 insertions(+), 35 deletions(-)
>>
>
> My bot found new DTB warnings on the .dts files added or changed in this
> series.

Please note that this is happening because the bot didn't account for
header changes in the previous USIv1 patchset. Should be safe to apply
since the latter is in linux-next now (if it even merges).

Best regards,
Ivaylo

>
> 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/arm64/boot/dts/exynos/' for 20250209132043.3906127-1-ivo.ivanov.ivanov1@gmail.com:
>
> Error: arch/arm64/boot/dts/exynos/exynos850.dtsi:654.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[3]: *** [scripts/Makefile.dtbs:131: arch/arm64/boot/dts/exynos/exynos850-e850-96.dtb] Error 1
> make[2]: *** [scripts/Makefile.build:465: arch/arm64/boot/dts/exynos] Error 2
> make[2]: Target 'arch/arm64/boot/dts/exynos/exynos850-e850-96.dtb' not remade because of errors.
> make[1]: *** [/home/rob/proj/linux-dt-testing/Makefile:1464: exynos/exynos850-e850-96.dtb] Error 2
> Error: arch/arm64/boot/dts/exynos/exynosautov920.dtsi:309.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[3]: *** [scripts/Makefile.dtbs:131: arch/arm64/boot/dts/exynos/exynosautov920-sadk.dtb] Error 1
> make[2]: *** [scripts/Makefile.build:465: arch/arm64/boot/dts/exynos] Error 2
> make[2]: Target 'arch/arm64/boot/dts/exynos/exynosautov920-sadk.dtb' not remade because of errors.
> make[1]: *** [/home/rob/proj/linux-dt-testing/Makefile:1464: exynos/exynosautov920-sadk.dtb] Error 2
> Error: arch/arm64/boot/dts/exynos/exynosautov9.dtsi:445.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[3]: *** [scripts/Makefile.dtbs:131: arch/arm64/boot/dts/exynos/exynosautov9-sadk.dtb] Error 1
> make[2]: *** [scripts/Makefile.build:465: arch/arm64/boot/dts/exynos] Error 2
> make[2]: Target 'arch/arm64/boot/dts/exynos/exynosautov9-sadk.dtb' not remade because of errors.
> make[1]: *** [/home/rob/proj/linux-dt-testing/Makefile:1464: exynos/exynosautov9-sadk.dtb] Error 2
> Error: arch/arm64/boot/dts/exynos/google/gs101.dtsi:828.20-21 syntax error
> FATAL ERROR: Unable to parse input tree
> make[4]: *** [scripts/Makefile.dtbs:131: arch/arm64/boot/dts/exynos/google/gs101-oriole.dtb] Error 1
> make[3]: *** [scripts/Makefile.build:465: arch/arm64/boot/dts/exynos/google] Error 2
> make[3]: Target 'arch/arm64/boot/dts/exynos/google/gs101-oriole.dtb' not remade because of errors.
> make[2]: *** [scripts/Makefile.build:465: arch/arm64/boot/dts/exynos] Error 2
> make[2]: Target 'arch/arm64/boot/dts/exynos/google/gs101-oriole.dtb' not remade because of errors.
> make[1]: *** [/home/rob/proj/linux-dt-testing/Makefile:1464: exynos/google/gs101-oriole.dtb] Error 2
> make: *** [Makefile:251: __sub-make] Error 2
> make: Target 'exynos/exynos8895-dreamlte.dtb' not remade because of errors.
> make: Target 'exynos/exynos850-e850-96.dtb' not remade because of errors.
> make: Target 'exynos/exynos7885-jackpotlte.dtb' not remade because of errors.
> make: Target 'exynos/exynos990-x1slte.dtb' not remade because of errors.
> make: Target 'exynos/exynos5433-tm2.dtb' not remade because of errors.
> make: Target 'exynos/exynos990-r8s.dtb' not remade because of errors.
> make: Target 'exynos/exynos7-espresso.dtb' not remade because of errors.
> make: Target 'exynos/google/gs101-oriole.dtb' not remade because of errors.
> make: Target 'exynos/exynosautov920-sadk.dtb' not remade because of errors.
> make: Target 'exynos/exynosautov9-sadk.dtb' not remade because of errors.
> make: Target 'exynos/exynos990-c1s.dtb' not remade because of errors.
> make: Target 'exynos/exynos9810-starlte.dtb' not remade because of errors.
> make: Target 'exynos/exynos990-x1s.dtb' not remade because of errors.
> make: Target 'exynos/exynos5433-tm2e.dtb' not remade because of errors.
>
>
>
>
>


  reply	other threads:[~2025-02-15 13:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-09 13:20 Ivaylo Ivanov
2025-02-10 16:22 ` Rob Herring (Arm)
2025-02-15 13:52   ` Ivaylo Ivanov [this message]
2025-04-16  7:38 ` 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=8bcf7557-dff3-4017-84b1-184b20e028bf@gmail.com \
    --to=ivo.ivanov.ivanov1@gmail.com \
    --cc=alim.akhtar@samsung.com \
    --cc=andre.draszik@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=peter.griffin@linaro.org \
    --cc=robh@kernel.org \
    --cc=semen.protsenko@linaro.org \
    --cc=tudor.ambarus@linaro.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

all inboxes | Powered by JetHome®