From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Mika Westerberg <mika.westerberg@linux.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: Mon, 28 Sep 2026 11:15:09 +0300 [thread overview]
Message-ID: <aroiDQV_p0isAQo5@ashevche-desk.local> (raw)
In-Reply-To: <20260926100727.GB106095@black.igk.intel.com>
On Sat, Sep 26, 2026 at 12:07:27PM +0200, Mika Westerberg wrote:
> On Fri, Sep 25, 2026 at 05:34:53PM +0300, Andy Shevchenko wrote:
> > 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:
...
> > > > > 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?
>
> I don't expect these two drives to get too much attention, and they could
> be contained nicely inside intel folder and that would help Bart to
> identify that these are Intel drivers. So your bandwidth would not suffer
> even if these two are added there. Your call.
I'll be happy to have a co-maintainer record to be added!
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-28 8:15 UTC|newest]
Thread overview: 24+ 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
2026-09-25 14:34 ` Andy Shevchenko
2026-09-26 10:07 ` Mika Westerberg
2026-09-28 8:15 ` Andy Shevchenko [this message]
2026-09-28 11:13 ` Bartosz Golaszewski
2026-09-28 11:34 ` Andy Shevchenko
2026-09-28 12:25 ` Bartosz Golaszewski
2026-09-28 13:12 ` Andy Shevchenko
2026-09-28 14:13 ` Bartosz Golaszewski
2026-09-28 14:33 ` Hans de Goede
2026-09-28 15:12 ` Andy Shevchenko
2026-09-28 17:06 ` Bartosz Golaszewski
2026-09-28 18:11 ` Andy Shevchenko
2026-09-28 12:34 ` Mika Westerberg
2026-09-28 13:13 ` Andy Shevchenko
2026-09-28 12:35 ` Hans de Goede
2026-09-28 13:10 ` Andy Shevchenko
2026-09-28 21:20 ` Sakari Ailus
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=aroiDQV_p0isAQo5@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=alan.borzeszkowski@linux.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=mika.westerberg@linux.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®