From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
Peter Tyser <ptyser@xes-inc.com>,
Lixu Zhang <lixu.zhang@intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>,
Mika Westerberg <westeri@kernel.org>,
Israel Cepeda <israel.a.cepeda.lopez@intel.com>,
Hans de Goede <hansg@kernel.org>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH RFC] gpio: move intel drivers into their own directory
Date: Fri, 25 Sep 2026 14:54:33 +0200 [thread overview]
Message-ID: <20260925125433.GY106095@black.igk.intel.com> (raw)
In-Reply-To: <arZRZfa7AmDxmwoJ@ashevche-desk.local>
Hi,
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.
next prev parent reply other threads:[~2026-09-25 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 10:22 Bartosz Golaszewski
2026-09-25 10:48 ` Andy Shevchenko
2026-09-25 11:42 ` Hans de Goede
2026-09-25 12:48 ` Andy Shevchenko
2026-09-25 14:39 ` Andy Shevchenko
2026-09-25 12:54 ` Mika Westerberg [this message]
2026-09-25 14:34 ` Andy Shevchenko
2026-09-25 16:17 ` 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=20260925125433.GY106095@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=bartosz.golaszewski@oss.qualcomm.com \
--cc=brgl@kernel.org \
--cc=hansg@kernel.org \
--cc=israel.a.cepeda.lopez@intel.com \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=ptyser@xes-inc.com \
--cc=sakari.ailus@linux.intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=westeri@kernel.org \
/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
all inboxes | Powered by JetHome®