[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <a0e3d45f-d982-4961-9945-3c81c0380806@kernel.org>
Date: Thu, 7 Nov 2024 10:34:07 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Wim Van Sebroeck <wim@...ana.be>
Cc: Byoungtae Cho <bt.cho@...sung.com>, Guenter Roeck <linux@...ck-us.net>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Sunyeal Hong <sunyeal.hong@...sung.com>, Taewan Kim
<trunixs.kim@...sung.com>, Wim Van Sebroeck <wim@...ux-watchdog.org>
Subject: Re: linux-next: manual merge of the watchdog tree with the
samsung-krzk tree
On 07/11/2024 06:59, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the watchdog tree got a conflict in:
>
> arch/arm64/boot/dts/exynos/exynosautov920.dtsi
>
> between commit:
>
> ef1c2a54cbc7 ("arm64: dts: exynosautov920: add peric1, misc and hsi0/1 clock DT nodes")
>
> from the samsung-krzk tree and commit:
>
> 3595a523d043 ("arm64: dts: exynosautov920: add watchdog DT node")
The main problem is above patch should have never been taken to watchdog
tree. I never agreed on that. I never acked it. It is against SoC
policies which are always requesting entire DTS to go through SoC tree.
Please drop the patch from watchdog. Or revert it.
Best regards,
Krzysztof
Powered by blists - more mailing lists