From: Guenter Roeck <linux@roeck-us.net>
To: Prabhakar <prabhakar.csengg@gmail.com>
Cc: Wim Van Sebroeck <wim@linux-watchdog.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-watchdog@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Prabhakar <prabhakar.csengg+renesas@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v2 2/2] watchdog: rzv2h: Drop WDTRCR_RSTIRQS macro
Date: Mon, 20 Jul 2026 07:57:58 -0700 [thread overview]
Message-ID: <cf85d5b6-7d9d-46a6-9ec5-ab0a17c9515f@roeck-us.net> (raw)
In-Reply-To: <20260715133922.2129340-3-prabhakar.mahadev-lad.rj@bp.renesas.com>
On Wed, Jul 15, 2026 at 02:39:22PM +0100, Prabhakar wrote:
> From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
>
> WDTRCR_RSTIRQS macro is unused so drop it.
Nit: This is a define, not a macro.
Thanks,
Guenter
>
> Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> ---
> v1->v2:
> - No changes.
> ---
> drivers/watchdog/rzv2h_wdt.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/watchdog/rzv2h_wdt.c b/drivers/watchdog/rzv2h_wdt.c
> index 0f951219caf8..3c8739902ec4 100644
> --- a/drivers/watchdog/rzv2h_wdt.c
> +++ b/drivers/watchdog/rzv2h_wdt.c
> @@ -40,8 +40,6 @@
> #define WDTCR_RPSS_25 0x00
> #define WDTCR_RPSS_100 0x3000
>
> -#define WDTRCR_RSTIRQS BIT(7)
> -
> #define WDTDCR_WDTSTOPCTRL BIT(0)
>
> #define WDT_DEFAULT_TIMEOUT 60U
next prev parent reply other threads:[~2026-07-20 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 13:39 [PATCH v2 0/2] watchdog: rzv2h: Convert WDTDCR handling to regmap Prabhakar
2026-07-15 13:39 ` [PATCH v2 1/2] " Prabhakar
2026-07-20 14:56 ` Guenter Roeck
2026-07-27 10:54 ` Lad, Prabhakar
2026-07-15 13:39 ` [PATCH v2 2/2] watchdog: rzv2h: Drop WDTRCR_RSTIRQS macro Prabhakar
2026-07-20 14:57 ` Guenter Roeck [this message]
2026-07-27 10:56 ` Lad, Prabhakar
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=cf85d5b6-7d9d-46a6-9ec5-ab0a17c9515f@roeck-us.net \
--to=linux@roeck-us.net \
--cc=biju.das.jz@bp.renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=prabhakar.csengg+renesas@gmail.com \
--cc=prabhakar.csengg@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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
all inboxes | Powered by JetHome®