All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Nicolas Schier <nicolas@fjasle.eu>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Conor Dooley <conor@kernel.org>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/4] kbuild: Per arch/platform dtc warning levels
Date: Thu, 23 Nov 2023 16:38:37 +0900	[thread overview]
Message-ID: <CAK7LNASVMjVg4dr=KdSDHwGww_47H78H7rMXA=wf+ncugesDSA@mail.gmail.com> (raw)
In-Reply-To: <20231122-dtc-warnings-v2-0-bd4087325392@kernel.org>

On Thu, Nov 23, 2023 at 7:12 AM Rob Herring <robh@kernel.org> wrote:
>
> This series adds support to set the dtc extra warning level on a per
> arch or per platform (directory really) basis.
>
> The first version of this was just a simple per directory override for
> Samsung platforms, but Conor asked to be able to do this for all of
> riscv.
>
> For merging, either I can take the whole thing or the riscv and samsung
> patches can go via their normal trees. The added variable will have no
> effect until merged with patch 2.
>
> v1:
>  - https://lore.kernel.org/all/20231116211739.3228239-1-robh@kernel.org/
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---


There were some attempts in the past to enable W=1 in particular subsystems,
so here is a similar comment.

Adding a new warning flag to W=1 is always safe without doing any compile test.

With this series, it would not be true any more because a new warning in W=1
would potentially break riscv/samsung platforms.

Linus requires a clean build (i.e. zero warning) when W= option is not given.






> Rob Herring (4):
>       kbuild: Move dtc graph_child_address warning to W=2
>       kbuild: Allow arch/platform override of dtc warning level
>       riscv: dts: Always enable extra W=1 warnings
>       arm/arm64: dts: samsung: Always enable extra W=1 warnings
>
>  arch/arm/boot/dts/samsung/Makefile  |  3 +++
>  arch/arm64/boot/dts/exynos/Makefile |  3 +++
>  arch/riscv/boot/dts/Makefile        |  3 +++
>  scripts/Makefile.lib                | 16 +++++++++-------
>  4 files changed, 18 insertions(+), 7 deletions(-)
> ---
> base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
> change-id: 20231122-dtc-warnings-968ff83a86ed
>
> Best regards,
> --
> Rob Herring <robh@kernel.org>
>


-- 
Best Regards
Masahiro Yamada

WARNING: multiple messages have this Message-ID (diff)
From: Masahiro Yamada <masahiroy@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	 Nicolas Schier <nicolas@fjasle.eu>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	 Conor Dooley <conor@kernel.org>,
	linux-kbuild@vger.kernel.org,  linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/4] kbuild: Per arch/platform dtc warning levels
Date: Thu, 23 Nov 2023 16:38:37 +0900	[thread overview]
Message-ID: <CAK7LNASVMjVg4dr=KdSDHwGww_47H78H7rMXA=wf+ncugesDSA@mail.gmail.com> (raw)
In-Reply-To: <20231122-dtc-warnings-v2-0-bd4087325392@kernel.org>

On Thu, Nov 23, 2023 at 7:12 AM Rob Herring <robh@kernel.org> wrote:
>
> This series adds support to set the dtc extra warning level on a per
> arch or per platform (directory really) basis.
>
> The first version of this was just a simple per directory override for
> Samsung platforms, but Conor asked to be able to do this for all of
> riscv.
>
> For merging, either I can take the whole thing or the riscv and samsung
> patches can go via their normal trees. The added variable will have no
> effect until merged with patch 2.
>
> v1:
>  - https://lore.kernel.org/all/20231116211739.3228239-1-robh@kernel.org/
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---


There were some attempts in the past to enable W=1 in particular subsystems,
so here is a similar comment.

Adding a new warning flag to W=1 is always safe without doing any compile test.

With this series, it would not be true any more because a new warning in W=1
would potentially break riscv/samsung platforms.

Linus requires a clean build (i.e. zero warning) when W= option is not given.






> Rob Herring (4):
>       kbuild: Move dtc graph_child_address warning to W=2
>       kbuild: Allow arch/platform override of dtc warning level
>       riscv: dts: Always enable extra W=1 warnings
>       arm/arm64: dts: samsung: Always enable extra W=1 warnings
>
>  arch/arm/boot/dts/samsung/Makefile  |  3 +++
>  arch/arm64/boot/dts/exynos/Makefile |  3 +++
>  arch/riscv/boot/dts/Makefile        |  3 +++
>  scripts/Makefile.lib                | 16 +++++++++-------
>  4 files changed, 18 insertions(+), 7 deletions(-)
> ---
> base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
> change-id: 20231122-dtc-warnings-968ff83a86ed
>
> Best regards,
> --
> Rob Herring <robh@kernel.org>
>


-- 
Best Regards
Masahiro Yamada

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: Masahiro Yamada <masahiroy@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>,
	 Nicolas Schier <nicolas@fjasle.eu>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	 Conor Dooley <conor@kernel.org>,
	linux-kbuild@vger.kernel.org,  linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org,  linux-riscv@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/4] kbuild: Per arch/platform dtc warning levels
Date: Thu, 23 Nov 2023 16:38:37 +0900	[thread overview]
Message-ID: <CAK7LNASVMjVg4dr=KdSDHwGww_47H78H7rMXA=wf+ncugesDSA@mail.gmail.com> (raw)
In-Reply-To: <20231122-dtc-warnings-v2-0-bd4087325392@kernel.org>

On Thu, Nov 23, 2023 at 7:12 AM Rob Herring <robh@kernel.org> wrote:
>
> This series adds support to set the dtc extra warning level on a per
> arch or per platform (directory really) basis.
>
> The first version of this was just a simple per directory override for
> Samsung platforms, but Conor asked to be able to do this for all of
> riscv.
>
> For merging, either I can take the whole thing or the riscv and samsung
> patches can go via their normal trees. The added variable will have no
> effect until merged with patch 2.
>
> v1:
>  - https://lore.kernel.org/all/20231116211739.3228239-1-robh@kernel.org/
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> ---


There were some attempts in the past to enable W=1 in particular subsystems,
so here is a similar comment.

Adding a new warning flag to W=1 is always safe without doing any compile test.

With this series, it would not be true any more because a new warning in W=1
would potentially break riscv/samsung platforms.

Linus requires a clean build (i.e. zero warning) when W= option is not given.






> Rob Herring (4):
>       kbuild: Move dtc graph_child_address warning to W=2
>       kbuild: Allow arch/platform override of dtc warning level
>       riscv: dts: Always enable extra W=1 warnings
>       arm/arm64: dts: samsung: Always enable extra W=1 warnings
>
>  arch/arm/boot/dts/samsung/Makefile  |  3 +++
>  arch/arm64/boot/dts/exynos/Makefile |  3 +++
>  arch/riscv/boot/dts/Makefile        |  3 +++
>  scripts/Makefile.lib                | 16 +++++++++-------
>  4 files changed, 18 insertions(+), 7 deletions(-)
> ---
> base-commit: b85ea95d086471afb4ad062012a4d73cd328fa86
> change-id: 20231122-dtc-warnings-968ff83a86ed
>
> Best regards,
> --
> Rob Herring <robh@kernel.org>
>


-- 
Best Regards
Masahiro Yamada

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2023-11-23  7:39 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 22:12 [PATCH v2 0/4] kbuild: Per arch/platform dtc warning levels Rob Herring
2023-11-22 22:12 ` Rob Herring
2023-11-22 22:12 ` Rob Herring
2023-11-22 22:12 ` [PATCH v2 1/4] kbuild: Move dtc graph_child_address warning to W=2 Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12 ` [PATCH v2 2/4] kbuild: Allow arch/platform override of dtc warning level Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12 ` [PATCH v2 3/4] riscv: dts: Always enable extra W=1 warnings Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12 ` [PATCH v2 4/4] arm/arm64: dts: samsung: " Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-22 22:12   ` Rob Herring
2023-11-23  7:18   ` Krzysztof Kozlowski
2023-11-23  7:18     ` Krzysztof Kozlowski
2023-11-23  7:18     ` Krzysztof Kozlowski
2023-11-23  7:38 ` Masahiro Yamada [this message]
2023-11-23  7:38   ` [PATCH v2 0/4] kbuild: Per arch/platform dtc warning levels Masahiro Yamada
2023-11-23  7:38   ` Masahiro Yamada
2023-11-23  9:43   ` Conor Dooley
2023-11-23  9:43     ` Conor Dooley
2023-11-23  9:43     ` Conor Dooley
2023-11-23 12:00     ` Masahiro Yamada
2023-11-23 12:00       ` Masahiro Yamada
2023-11-23 12:00       ` Masahiro Yamada
2023-11-27 14:03   ` Rob Herring
2023-11-27 14:03     ` Rob Herring
2023-11-27 14:03     ` Rob Herring
2023-11-28 12:02     ` Masahiro Yamada
2023-11-28 12:02       ` Masahiro Yamada
2023-11-28 12:02       ` Masahiro Yamada
2023-11-28 22:25       ` Rob Herring
2023-11-28 22:25         ` Rob Herring
2023-11-28 22:25         ` Rob Herring
2023-11-29 17:49         ` Masahiro Yamada
2023-11-29 17:49           ` Masahiro Yamada
2023-11-29 17:49           ` Masahiro Yamada
2023-11-23  9:47 ` Conor Dooley
2023-11-23  9:47   ` Conor Dooley
2023-11-23  9:47   ` 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='CAK7LNASVMjVg4dr=KdSDHwGww_47H78H7rMXA=wf+ncugesDSA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=robh@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 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.