All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Biju Das <biju.das.jz@bp.renesas.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH] arm64: dts: renesas: rzg2ul-smarc-som: Drop enabling wdt2
Date: Mon, 19 Sep 2022 10:47:51 +0100	[thread overview]
Message-ID: <CA+V-a8vDMFKJb0wDOR8LZifRDBa0hju-YgL_BDb0chVjpef98w@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVRmuQm5xRgpQurCJTu7goqNi5zj+Q9cLLz_s_p=znbbA@mail.gmail.com>

Hi Geert,

Thank you for the review.

On Sun, Sep 18, 2022 at 10:04 AM Geert Uytterhoeven
<geert@linux-m68k.org> wrote:
>
> On Wed, Sep 14, 2022 at 3:43 PM Prabhakar <prabhakar.csengg@gmail.com> wrote:
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> >
> > WDT CH2 is specifically to check the operation of Cortex-M33 CPU so
> > don't enable WDT2 by default.
> >
For consistency I'll drop enabling WDT2 from the RZ/G2L{C} too.

Cheers,
Prabhakar

  reply	other threads:[~2022-09-19  9:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 13:42 [PATCH] arm64: dts: renesas: rzg2ul-smarc-som: Drop enabling wdt2 Prabhakar
2022-09-18  9:04 ` Geert Uytterhoeven
2022-09-19  9:47   ` Lad, Prabhakar [this message]
2022-09-19 10:06     ` Biju Das
2022-09-19 10:10       ` Geert Uytterhoeven
2022-09-19 10:15         ` Biju Das
2022-09-19 10:44           ` Lad, Prabhakar
2022-09-19 10:55             ` Biju Das
2022-09-19 11:04               ` Lad, Prabhakar
2022-09-19 11:10                 ` Biju Das
2022-09-19 11:37                   ` Geert Uytterhoeven
2022-09-19 11:43                     ` Biju Das

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=CA+V-a8vDMFKJb0wDOR8LZifRDBa0hju-YgL_BDb0chVjpef98w@mail.gmail.com \
    --to=prabhakar.csengg@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.