Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Adjustments for pinctrl-amd debounce behavior
Date: Fri, 1 Aug 2025 18:36:54 +0530	[thread overview]
Message-ID: <3590cfd1-9d99-4781-bde5-0ace736b2158@amd.com> (raw)
In-Reply-To: <9469816e-6ae8-476e-b154-28c78a79bac8@amd.com>

On 8/1/2025 6:33 PM, Mario Limonciello wrote:
> Hi,
> 
> The issue that I originally fixed with
> 
> commit 8ff4fb276e23 ("pinctrl: amd: Clear GPIO debounce for suspend")
> 
> I have found out will be a problem on more platforms due to more designs 
> switching to power button controlled this way.
> 
> I think it would be a good idea to take it back to stable kernels.
> 
> Thanks!

Actually, I see that it already came to 6.15.7:

dce86a4d0d5b9e416b3787d624b711ffb3e03a52

So never mind!

      reply	other threads:[~2025-08-01 13:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-01 13:03 Adjustments for pinctrl-amd debounce behavior Mario Limonciello
2025-08-01 13:06 ` Mario Limonciello [this message]

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=3590cfd1-9d99-4781-bde5-0ace736b2158@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=stable@vger.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