From: Mario Limonciello <mario.limonciello@amd.com>
To: <torvalds@linux-foundation.org>
Cc: Natikar Basavaraj <Basavaraj.Natikar@amd.com>,
Gong Richard <Richard.Gong@amd.com>,
<regressions@lists.linux.dev>,
Thorsten Leemhuis <regressions@leemhuis.info>,
Greg KH <gregkh@linuxfoundation.org>, <stable@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"Bartosz Golaszewski" <brgl@bgdev.pl>,
Shreeya Patel <shreeya.patel@collabora.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"Mario Limonciello" <mario.limonciello@amd.com>
Subject: [PATCH v2 0/1] Fix regression in 5.18 for GPIO
Date: Fri, 22 Apr 2022 08:14:51 -0500 [thread overview]
Message-ID: <20220422131452.20757-1-mario.limonciello@amd.com> (raw)
Linus,
This patch is being sent directly to you because there has been
a regression in 5.18 that I identified and sent a fix up that has been
reviewed/tested/acked for nearly a week but the current subsystem
maintainer (Bartosz) hasn't picked it up to send to you.
It's a severe problem; anyone who hits it:
1) Power button doesn't work anymore
2) Can't resume their laptop from S3 or s2idle
Because the original patch was cc stable@, it landed in stable releases
and has been breaking people left and right as distros track the stable
channels. The patch is well tested. Would you please consider to pick
this up directly to fix that regression?
Thanks,
Mario Limonciello (1):
gpio: Request interrupts after IRQ is initialized
drivers/gpio/gpiolib.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2022-04-22 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:14 Mario Limonciello [this message]
2022-04-22 13:14 ` [PATCH v2 1/1] gpio: Request interrupts after IRQ is initialized Mario Limonciello
2022-04-22 14:38 ` Limonciello, Mario
2022-04-23 1:03 ` [PATCH v2 0/1] Fix regression in 5.18 for GPIO Linus Torvalds
2022-04-25 18:41 ` Bartosz Golaszewski
2022-04-25 18:42 ` Bartosz Golaszewski
2022-04-25 18:46 ` Limonciello, Mario
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=20220422131452.20757-1-mario.limonciello@amd.com \
--to=mario.limonciello@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=Richard.Gong@amd.com \
--cc=andy.shevchenko@gmail.com \
--cc=brgl@bgdev.pl \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=shreeya.patel@collabora.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).