From: Wim Van Sebroeck <wim@linux-watchdog.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Taewan Kim <trunixs.kim@samsung.com>,
Guenter Roeck <linux@roeck-us.net>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Byoungtae Cho <bt.cho@samsung.com>
Subject: Re: [PATCH v3 3/3] arm64: dts: exynosautov920: add watchdog DT node
Date: Thu, 7 Nov 2024 12:33:25 +0100 [thread overview]
Message-ID: <20241107113325.GA5284@www.linux-watchdog.org> (raw)
In-Reply-To: <589c40e1-6a1c-4ef7-b0d8-b761b132578a@kernel.org>
Hi Krzystof,
> On 07/11/2024 11:33, Wim Van Sebroeck wrote:
> > Hi Krzystof,
> >
> >> On 21/10/2024 08:39, Taewan Kim wrote:
> >>> From: Byoungtae Cho <bt.cho@samsung.com>
> >>>
> >>> Adds two watchdog devices for ExynosAutoV920 SoC.
> >>>
> >>> Signed-off-by: Byoungtae Cho <bt.cho@samsung.com>
> >>> Signed-off-by: Taewan Kim <trunixs.kim@samsung.com>
> >>> ---
> >>> .../arm64/boot/dts/exynos/exynosautov920.dtsi | 20 +++++++++++++++++++
> >>> 1 file changed, 20 insertions(+)
> >>
> >> How did this happen that this patch was taken to watchdog? There is no
> >> Ack here from me.
> >>
> >> Drop this patch from watchdog, I do no agree to take it via that tree.
> >>
> >> Best regards,
> >> Krzysztof
> >>
> >
> > Seems like you are having a hard day.
> > The 3 patches are dropped. I presume that you will take them all through your tree then?
>
> I meant only this one patch, not entire patchset. The bindings and
> watchdog driver are for you. I commented only about this patch here - DTS.
>
>
> Best regards,
> Krzysztof
>
I added the first two patches again. Even when it sounds more logical to me to keep the 3 together. But that's a never ending discussion, so we won't go into that :-).
Kind regards,
Wim.
next prev parent reply other threads:[~2024-11-07 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20241021063937epcas2p40b368212fc236cd916492f0ed342671d@epcas2p4.samsung.com>
2024-10-21 6:39 ` [PATCH v3 0/3] support watchdog for exynosautov920 Taewan Kim
2024-10-21 6:39 ` [PATCH v3 1/3] dt-bindings: watchdog: Document ExynosAutoV920 watchdog bindings Taewan Kim
2024-10-21 6:39 ` [PATCH v3 2/3] watchdog: s3c2410_wdt: add support for exynosautov920 SoC Taewan Kim
2024-10-21 6:39 ` [PATCH v3 3/3] arm64: dts: exynosautov920: add watchdog DT node Taewan Kim
2024-11-07 9:32 ` Krzysztof Kozlowski
2024-11-07 10:33 ` Wim Van Sebroeck
2024-11-07 11:37 ` Krzysztof Kozlowski
2024-11-07 11:33 ` Wim Van Sebroeck [this message]
2024-11-07 12:08 ` Krzysztof Kozlowski
2024-12-05 0:28 ` 김태완
2024-12-05 7:19 ` Krzysztof Kozlowski
2024-12-05 10:35 ` Krzysztof Kozlowski
2024-12-05 12:25 ` 김태완
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=20241107113325.GA5284@www.linux-watchdog.org \
--to=wim@linux-watchdog.org \
--cc=alim.akhtar@samsung.com \
--cc=bt.cho@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh@kernel.org \
--cc=trunixs.kim@samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox