From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: '김태완' <trunixs.kim@samsung.com>,
"'Sam Protsenko'" <semen.protsenko@linaro.org>
Cc: "'Wim Van Sebroeck'" <wim@linux-watchdog.org>,
"'Guenter Roeck'" <linux@roeck-us.net>,
"'Rob Herring'" <robh@kernel.org>,
"'Krzysztof Kozlowski'" <krzk+dt@kernel.org>,
"'Conor Dooley'" <conor+dt@kernel.org>,
<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 2/3] watchdog: s3c2410_wdt: add support for exynosautov920 SoC
Date: Thu, 10 Oct 2024 13:15:05 +0530 [thread overview]
Message-ID: <005c01db1ae8$544a1e40$fcde5ac0$@samsung.com> (raw)
In-Reply-To: <000101db1ae5$96c111f0$c44335d0$@samsung.com>
Hi Taewan
> -----Original Message-----
> From: 김태완 <trunixs.kim@samsung.com>
> Sent: Thursday, October 10, 2024 12:56 PM
> To: 'Sam Protsenko' <semen.protsenko@linaro.org>
> Cc: 'Wim Van Sebroeck' <wim@linux-watchdog.org>; '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 2/3] watchdog: s3c2410_wdt: add support for
> exynosautov920 SoC
>
> Hi,
>
> Thank you for your review.
> Yes, cl0 is correct not cl1.
> I will apply it to v2 patch.
>
Don’t send a top up reply, context get lost. Configure your email client properly to send a inline reply.
> Best regards,
> Taewan Kim.
>
next prev parent reply other threads:[~2024-10-10 7:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240913080347epcas2p222e2536e026f90bb12c18e640fd05e8e@epcas2p2.samsung.com>
2024-09-13 8:03 ` [PATCH 0/3] support watchdog for exynosautov920 Taewan Kim
[not found] ` <CGME20240913080347epcas2p3f92c8fe85b252f8ac2033261db345837@epcas2p3.samsung.com>
2024-09-13 8:03 ` [PATCH 1/3] dt-bindings: watchdog: Document ExynosAutoV920 watchdog bindings Taewan Kim
2024-09-21 0:30 ` Rob Herring (Arm)
2024-09-30 12:05 ` Krzysztof Kozlowski
[not found] ` <CGME20240913080347epcas2p4b5694797cff88a22fd815a9de989d20b@epcas2p4.samsung.com>
2024-09-13 8:03 ` [PATCH 2/3] watchdog: s3c2410_wdt: add support for exynosautov920 SoC Taewan Kim
2024-09-30 12:04 ` Krzysztof Kozlowski
2024-10-10 7:21 ` 김태완
2024-09-30 14:51 ` Guenter Roeck
2024-09-30 20:14 ` Sam Protsenko
2024-10-10 7:25 ` 김태완
2024-10-10 7:45 ` Alim Akhtar [this message]
2024-10-21 3:59 ` 김태완
[not found] ` <CGME20240913080347epcas2p46fd90107fe54b8eab3a031cf2fbd592c@epcas2p4.samsung.com>
2024-09-13 8:03 ` [PATCH 3/3] arm64: dts: exynosautov920: add watchdog DT node Taewan Kim
2024-09-30 11:37 ` Krzysztof Kozlowski
2024-10-10 7:30 ` 김태완
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='005c01db1ae8$544a1e40$fcde5ac0$@samsung.com' \
--to=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=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=semen.protsenko@linaro.org \
--cc=trunixs.kim@samsung.com \
--cc=wim@linux-watchdog.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;
as well as URLs for NNTP newsgroup(s).