From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Vasu <vasuhansalia05@gmail.com>
Cc: platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
djrscally@gmail.com, mika.westerberg@linux.intel.com
Subject: Re: [PATCH 2/2] platform/x86: int3472: Handle GPIO types 0x02 and 0x12 for Lunar Lake
Date: Sun, 5 Apr 2026 19:10:54 +0300 [thread overview]
Message-ID: <adKJjmcdrgS_X8wL@ashevche-desk.local> (raw)
In-Reply-To: <20260405092714.6203-1-vasuhansalia05@gmail.com>
On Sun, Apr 05, 2026 at 02:57:14PM +0530, Vasu wrote:
> After checking the mainline kernel source, I found that
> INT3472_GPIO_TYPE_HANDSHAKE (0x12) is already defined and fully
> handled in mainline. So no v2 patch is needed for mainline.
>
> The fix just needs to be backported to the Ubuntu OEM kernels
> (6.11-oem, 6.17-oem) where affected users are running Ubuntu 24.04.
>
> Should I send a backport request to the Ubuntu kernel team, or is
> there another process you would recommend?
It's documented:
Documentation/process/stable-kernel-rules.rst
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-04-05 16:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-04 19:02 [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID for Lunar Lake Vasu
2026-04-04 19:02 ` [PATCH 2/2] platform/x86: int3472: Handle GPIO types 0x02 and 0x12 " Vasu
2026-04-04 19:55 ` Andy Shevchenko
2026-04-05 1:34 ` Vasu
2026-04-05 9:01 ` Andy Shevchenko
2026-04-05 9:15 ` Vasu
2026-04-05 9:27 ` Vasu
2026-04-05 16:10 ` Andy Shevchenko [this message]
2026-04-04 19:52 ` [PATCH 1/2] pinctrl: intel: platform: Add INTC10B5 ACPI ID " Andy Shevchenko
2026-04-05 1:34 ` Vasu
2026-04-05 8:59 ` Andy Shevchenko
2026-04-05 9:15 ` Vasu
2026-04-05 16:17 ` Andy Shevchenko
2026-04-05 16:33 ` Vasu
2026-04-05 2:07 ` Vasu
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=adKJjmcdrgS_X8wL@ashevche-desk.local \
--to=andriy.shevchenko@linux.intel.com \
--cc=djrscally@gmail.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vasuhansalia05@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.