From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sangwook Shin <sw617.shin@samsung.com>,
alim.akhtar@samsung.com, wim@linux-watchdog.org,
linux@roeck-us.net
Cc: linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
linux-watchdog@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND 4/5] watchdog: s3c2410_wdt: exynosautov920: Enable QUIRK_HAS_32BIT_MAXCNT
Date: Mon, 14 Jul 2025 08:04:16 +0200 [thread overview]
Message-ID: <6e96a7ac-5e29-4e04-98a9-2f0a7d506ffe@kernel.org> (raw)
In-Reply-To: <20250714055440.3138135-5-sw617.shin@samsung.com>
On 14/07/2025 07:54, Sangwook Shin wrote:
> Enable QUIRK_HAS_32BIT_MAXCNT to ExynosAutov920 SoC which has 32-bit WTCNT.
>
> Signed-off-by: Sangwook Shin <sw617.shin@samsung.com>
> ---
> drivers/watchdog/s3c2410_wdt.c | 4 ++--
This should be squashed with previous patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-07-14 6:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250714055850epcas2p454265f0cc65a80e80e536a4e88819e2a@epcas2p4.samsung.com>
2025-07-14 5:54 ` [PATCH v3 RESEND 0/5] Increase max timeout value of s3c2410 watchdog Sangwook Shin
2025-07-14 5:54 ` [PATCH v3 RESEND 1/5] watchdog: s3c2410_wdt: Replace hardcoded values with macro definitions Sangwook Shin
2025-07-24 5:53 ` Alim Akhtar
2025-07-24 7:14 ` Sam Protsenko
2025-07-14 5:54 ` [PATCH v3 RESEND 2/5] watchdog: s3c2410_wdt: Fix max_timeout being calculated larger Sangwook Shin
2025-07-24 5:53 ` Alim Akhtar
2025-07-14 5:54 ` [PATCH v3 RESEND 3/5] watchdog: s3c2410_wdt: Increase max timeout value of watchdog Sangwook Shin
2025-07-14 6:04 ` Krzysztof Kozlowski
2025-07-14 8:17 ` sw617.shin
2025-07-24 5:57 ` Alim Akhtar
2025-07-14 5:54 ` [PATCH v3 RESEND 4/5] watchdog: s3c2410_wdt: exynosautov920: Enable QUIRK_HAS_32BIT_MAXCNT Sangwook Shin
2025-07-14 6:04 ` Krzysztof Kozlowski [this message]
2025-07-14 5:54 ` [PATCH v3 RESEND 5/5] watchdog: s3c2410_wdt: exynosautov9: Enable supported features Sangwook Shin
2025-07-24 5:58 ` Alim Akhtar
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=6e96a7ac-5e29-4e04-98a9-2f0a7d506ffe@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--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=sw617.shin@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