Re: [PATCH v1 0/5] gpio: Move most of the Intel GPIO to the dedicated folder

[Andy Shevchenko <andriy.shevchenko@linux.intel.com>]

On Mon, Nov 02, 2026 at 10:48:42PM +0200, Andy Shevchenko wrote:
> On Mon, Nov 2, 2026 at 5:33 PM Bartosz Golaszewski <brgl@kernel.org> wrote:
> > On Fri, Sep 25, 2026 at 05:57:02PM +0200, Andy Shevchenko wrote:
> > > For the easier maintenance and future development move most of Intel GPIO
> > > drivers to the dedicated 'intel' folder. For now it only covers the drivers
> > > I maintain (as per record in the MAINTAINERS).
> >
> > I wanted to apply this in order to see how the menuconfig looks like
> > with it but it doesn't apply neither to next/master nor v7.4-rc1.
> 
> I will check this as soon as I can (currently I have something else to
> address which is more urgent and it's not related to Linux at all).

Actually I can't do it right now as it will be a race with the incoming
patches (for example, I see gpio-sodaville change in the mailing list).
Can you tell me when it will be the time that

1) your for-current is present in for-next (so no merging conflicts)
2) your for-next is closed for new patches for a few days?

Only with that I can achieve some good result, otherwise you will always
tell me to rebase/resend and while I do this, there will be a chance of
a new contribution that continues the loop.

TL;DR: I truly believe that the best timing for such a series is just
after the -rc1 as a first batch against for-current *and* for-next
(same piece assumed to go to -rc2). But of course, we may resolve
the potential conflicts.

So, what do you think?

-- 
With Best Regards,
Andy Shevchenko