Re: [PATCH RFC] gpio: move intel drivers into their own directory

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

On Fri, Sep 25, 2026 at 02:54:33PM +0200, Mika Westerberg wrote:
> On Fri, Sep 25, 2026 at 01:48:05PM +0300, Andy Shevchenko wrote:
> > On Fri, Sep 25, 2026 at 12:22:15PM +0200, Bartosz Golaszewski wrote:
> > > In order to avoid maintainer mistakes on patch ownership: move all the
> > > Intel drivers into their own dedicated directory under
> > > drivers/gpio/intel. Don't touch Kconfig options as we historically sort
> > > GPIO drivers by type, not by vendor.

...

> > >  drivers/gpio/{ => intel}/gpio-graniterapids.c   |  0
> > >  drivers/gpio/{ => intel}/gpio-novalake-events.c |  0
> > 
> > These are interesting drivers, not sure where to put them
> 
> IMHO they should be there too. We are maintaining them both.

Do you send PRs to Bart or you just rely on him to take the patches?

The whole problem started from clashing in MAINTAINERS. If you plan to
be part of the intel/ subfolder then I assume you want to be part of
some common Intel GPIO repository / maintenance. So far I have the majority
of the Intel GPIO drivers to go via my tree.

TL;DR: whatever is related to Intel, but not currently goes via my tree,
I leave to the respective maintainers to decide what to do.

So USB/novalake/graniterapids all have own maintainers, so for now I leave
them under drivers/gpio.

-- 
With Best Regards,
Andy Shevchenko