[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <173126574727.7785.4094963648273280544.b4-ty@linaro.org>
Date: Sun, 10 Nov 2024 20:10:31 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: linux-gpio@...r.kernel.org,
Conor Dooley <conor@...nel.org>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Conor Dooley <conor.dooley@...rochip.com>,
Daire McNamara <daire.mcnamara@...rochip.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>,
linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH v1 0/2] polarfire gpio driver follow-ups
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Thu, 07 Nov 2024 10:33:39 +0000, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@...rochip.com>
>
> Yo,
>
> I realised last week, while rebasing the interrupt portion of the
> driver, that coregpio a compatible in the kernel as well as a dts user.
> Given how long the driver has taken to even get partially accepted, I
> waited to get it to gpio/for-next rather than showing up with last
> minute additions to it.
>
> [...]
Applied, thanks!
I must admit I like your b4 topic names. :)
[2/2] MAINTAINERS: add gpio driver to PolarFire entry
commit: 10287f0f9ee91f75a60ec1b19d962f459b18f589
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists