devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Herring <robh@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: "Herve Codina (Schneider Electric)" <herve.codina@bootlin.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	Saravana Kannan <saravanak@google.com>,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Pascal Eberhard <pascal.eberhard@se.com>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC
Date: Wed, 7 Jan 2026 20:13:52 +0100	[thread overview]
Message-ID: <aV6wcIE0D7ozKeQn@ninjato> (raw)
In-Reply-To: <CAMuHMdXTZ2LDs-nFQRh+Q5YAW_LD+j6j=Mzv0RxyB-1wnJgbuQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]


> > I think this series is ready and I would really like to see it upstream
> > soon. I wonder, however, if the path to upstream has already been
> > discussed? It touches various subsystems, so I don't see immediately who
> > should pick the whole series? Or if parts should go to different
> > subsystems offering immutable branches? I bring this up because I want
> > to avoid losing a cycle just because this is unclear...
> 
> We actually did[1]. Unfortunately that plan was never executed.
> The DTS patches I can easily take through renesas-devel, as they have
> no hard dependencies.
> For the remaining patches, I see two options:
>   A. Rob takes the first two patches, and provides an immutable branch.
>      Then Thomas takes the irqchip patches, and I take the rest.
>   B. Rob and Thomas provide acks, and I take the whole series.

B) should be the easiest for everyone. Rob, Thomas, are you okay to ack
these patches? If no reply here, maybe a resend is in place with proper
description of the suggested path upstream in the cover letter?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2026-01-07 19:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-15 14:28 [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 1/8] of/irq: Introduce for_each_of_imap_item Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 2/8] of: unittest: Add a test case for for_each_of_imap_item iterator Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 3/8] irqchip/ls-extirq: Use " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 4/8] irqchip/renesas-rza1: " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 5/8] ARM: dts: r9a06g032: Add GPIO controllers Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 6/8] dt-bindings: soc: renesas: Add the Renesas RZ/N1 GPIO Interrupt Multiplexer Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 7/8] soc: renesas: Add support for " Herve Codina (Schneider Electric)
2025-12-15 14:28 ` [PATCH v7 8/8] ARM: dts: r9a06g032: Add support for GPIO interrupts Herve Codina (Schneider Electric)
2025-12-20  6:41   ` Wolfram Sang
2025-12-20  6:37 ` [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC Wolfram Sang
2025-12-22 15:35   ` Geert Uytterhoeven
2026-01-07 19:13     ` Wolfram Sang [this message]

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=aV6wcIE0D7ozKeQn@ninjato \
    --to=wsa+renesas@sang-engineering.com \
    --cc=brgl@bgdev.pl \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=herve.codina@bootlin.com \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=pascal.eberhard@se.com \
    --cc=robh@kernel.org \
    --cc=saravanak@google.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.petazzoni@bootlin.com \
    /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).