Devicetree
 help / color / mirror / Atom feed
From: Dan Scally <dan.scally@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Walleij <linusw@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Rob Herring <robh@kernel.org>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes
Date: Wed, 7 Oct 2026 11:28:38 +0100	[thread overview]
Message-ID: <6e22143e-92f0-4611-90df-9d1674083cff@ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdVMt95DBV1DeLa5zVkMV4sYj8v_uA1TTJiZFi_QKvMkAA@mail.gmail.com>

Hi Geert

On 25/09/2026 11:10, Geert Uytterhoeven wrote:
> Hi Dan,
> 
> On Fri, 25 Sept 2026 at 11:48, Dan Scally <dan.scally@ideasonboard.com> wrote:
>> Huh; not sure why I never followed up on this. I haven't touched the board in some time, so it must
>> have slipped my mind. I can pick it back up and address the comments, including adding the other
>> interrupts.
> 
> Same for "[PATCH] arm64: dts: renesas: r9a09g057h48-kakip: Enable eth0"?

Ah - yes! I'll revive that since Linus is handling the IVC / ISP ones

Thanks
Dan

> Thanks!
> 
> Gr{oetje,eeting}s,
> 
>                          Geert
> 


  reply	other threads:[~2026-10-07 10:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 13:33 [PATCH 0/2] arm64: dts: renesas: Enable ISP and IVC on RZ/V2H EVK Linus Walleij
2026-09-22 13:34 ` [PATCH 1/2] arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes Linus Walleij
2026-09-23  9:58   ` Geert Uytterhoeven
2026-09-23 17:17     ` Linus Walleij
2026-09-25  9:48       ` Dan Scally
2026-09-25 10:10         ` Geert Uytterhoeven
2026-10-07 10:28           ` Dan Scally [this message]
2026-09-25 12:03         ` Linus Walleij
2026-09-22 13:34 ` [PATCH 2/2] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Add ISP and IVC nodes Linus Walleij
2026-09-23  9:59   ` Geert Uytterhoeven
2026-09-25  9:30   ` Laurent Pinchart

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=6e22143e-92f0-4611-90df-9d1674083cff@ideasonboard.com \
    --to=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox