public inbox for linux-gpio@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Yixun Lan <dlan@gentoo.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	Alex Elder <elder@riscstar.com>,
	Inochi Amaoto <inochiama@gmail.com>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	linux-riscv@lists.infradead.org, spacemit@lists.linux.dev
Subject: Re: [PATCH v3 2/2] gpiolib: support parsing gpio three-cell interrupts scheme
Date: Tue, 08 Apr 2025 10:47:36 +0200	[thread overview]
Message-ID: <87r023ujiv.ffs@tglx> (raw)
In-Reply-To: <CAMRc=MeFK1gX69CWH2gkYUqkLU-KCOcwHcA+gjN1RXFA++B_eQ@mail.gmail.com>

On Mon, Apr 07 2025 at 13:26, Bartosz Golaszewski wrote:
> On Mon, Apr 7, 2025 at 12:33 PM Yixun Lan <dlan@gentoo.org> wrote:
>> On 06:06 Wed 26 Mar     , Yixun Lan wrote:
>>   I'd assume this patch [2/2] will go via pinctrl's tree?
>> as patch [1/2] has been accepted by Thomas into tip tree [1]..
>>   Additonally need to pull that commit first? since it's a dependency
>>
>
> No, this should go through the GPIO tree but for that I'd need an
> immutable tag with patch 1/2.

Here you go:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irqdomain-04-08-25

Thanks,

        tglx

  reply	other threads:[~2025-04-08  8:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 22:06 [PATCH v3 0/2] gpio: irq: support describing three-cell interrupts Yixun Lan
2025-03-25 22:06 ` [PATCH v3 1/2] irqdomain: support three-cell scheme interrupts Yixun Lan
2025-03-25 22:06 ` [PATCH v3 2/2] gpiolib: support parsing gpio three-cell interrupts scheme Yixun Lan
2025-04-07 10:33   ` Yixun Lan
2025-04-07 11:26     ` Bartosz Golaszewski
2025-04-08  8:47       ` Thomas Gleixner [this message]
2025-04-08  8:59         ` Bartosz Golaszewski
2025-04-08  9:03   ` Bartosz Golaszewski
2025-04-08 11:53     ` Yixun Lan
2025-04-08  7:23 ` [PATCH v3 0/2] gpio: irq: support describing three-cell interrupts Geert Uytterhoeven
2025-04-15  7:32 ` Linus Walleij

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=87r023ujiv.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=brgl@bgdev.pl \
    --cc=dlan@gentoo.org \
    --cc=elder@riscstar.com \
    --cc=inochiama@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=spacemit@lists.linux.dev \
    /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