(subset) [PATCH v4 0/4] gpio: realtek: Add support for Realtek DHC RTD1625

[Bartosz Golaszewski]

On Tue, 7 Jul 2026 09:57:19 +0200, "andriy.shevchenko at intel.com"
<andriy.shevchenko at intel.com> said:
> On Tue, Jul 07, 2026 at 12:24:16AM -0700, Bartosz Golaszewski wrote:
>> On Tue, 7 Jul 2026 08:55:26 +0200, "Yu-Chun Lin [林祐君]"
>> <eleanor.lin at realtek.com> said:
>> >> On Mon, 22 Jun 2026 17:23:31 +0800, Yu-Chun Lin wrote:
>
> [...]
>
>> >> Applied, thanks!
>> >>
>> >> [1/4] dt-bindings: gpio: realtek: Add realtek,rtd1625-gpio
>> >>
>> >> https://git.kernel.org/brgl/c/8f32808e1530b2229e07695fb39c54fee910bd4a
>> >> [2/4] gpio: Replace "default y" with "default ARCH_REALTEK" in Kconfig
>> >>
>> >> https://git.kernel.org/brgl/c/b5d23fcdb12972c522e96f90ab48be8a0d971b0e
>> >> [3/4] gpio: realtek: Add driver for Realtek DHC RTD1625 SoC
>> >>
>> >> https://git.kernel.org/brgl/c/a57e27c43b0315ee86c6896510d69be5257e093e
>> >
>> > Thank you for applying the patches!
>> >
>> > I'm currently working on v6 of the patch series that incorporates Andy's
>> > gpio-regmap patches, and it should build on top of gpio/for-next. However,
>> > I have a conflict with the driver patch that was already applied.
>> >
>> > Could you please revert that commit from gpio/for-next?
>>
>> Can you just post the series as a follow-up? I try to avoid rebases unless
>> absolutely necessary.
>
> Would be just leading reverts in the series appropriate? Otherwise it will give
> a lot of additional work for peanuts.
>

Yes, that's alright. It will make the review easier. We can then squash the
reverts with the new patches when applying.

Bart