From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-gpio@vger.kernel.org, linusw@kernel.org,
Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
Subject: Re: [PATCH v2] gpio: Add Intel Nova Lake ACPI GPIO events driver
Date: Sat, 4 Apr 2026 22:44:59 +0300 [thread overview]
Message-ID: <adFqO94IE-jUk-i4@ashevche-desk.local> (raw)
In-Reply-To: <CAMRc=MekQqNXM1MRfFOgF-3Vp_TX46soqLvKGfXZ=1P0XyFJPA@mail.gmail.com>
On Fri, Apr 03, 2026 at 05:30:56AM -0700, Bartosz Golaszewski wrote:
> On Thu, 2 Apr 2026 11:45:18 +0200, Mika Westerberg
> <mika.westerberg@linux.intel.com> said:
> > On Wed, Apr 01, 2026 at 07:45:26PM +0200, Alan Borzeszkowski wrote:
> >> This driver provides support for new way of handling platform events,
> >> through the use of GPIO-signaled ACPI events. This mechanism is used on
> >> Intel client platforms released in 2026 and later, starting with Intel
> >> Nova Lake.
> >>
> >> Signed-off-by: Alan Borzeszkowski <alan.borzeszkowski@linux.intel.com>
> >
> > Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Should I queue it for v7.1 or will Andy pick it up?
It's unrelated to real GPIO HW drivers I handle. So, please take it.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-04 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 17:45 [PATCH v2] gpio: Add Intel Nova Lake ACPI GPIO events driver Alan Borzeszkowski
2026-04-02 9:45 ` Mika Westerberg
2026-04-03 12:30 ` Bartosz Golaszewski
2026-04-04 19:44 ` Andy Shevchenko [this message]
2026-04-07 9:51 ` Linus Walleij
2026-04-07 10:44 ` Bartosz Golaszewski
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=adFqO94IE-jUk-i4@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=alan.borzeszkowski@linux.intel.com \
--cc=brgl@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).