All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: firew4lker <firew4lker@gmail.com>,
	Bartosz Golaszewski <brgl@bgdev.pl>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	Shreeya Patel <shreeya.patel@collabora.com>,
	"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Basavaraj.Natikar@amd.com, Richard.Gong@amd.com,
	stable@vger.kernel.org
Subject: Re: [PATCH] gpio: Request interrupts after IRQ is initialized
Date: Wed, 20 Apr 2022 00:02:16 +0200	[thread overview]
Message-ID: <CACRpkdbvN0ZJnn+N=Vt2n_aO4CnM=E4qpe_3dmu-c8_Ufp8ZzQ@mail.gmail.com> (raw)
In-Reply-To: <67df4178-5943-69d8-0d61-f533671a1248@amd.com>

On Mon, Apr 18, 2022 at 6:34 AM Mario Limonciello
<mario.limonciello@amd.com> wrote:

> Linus Walleij,
>
> As this is backported to 5.15.y, 5.16.y, 5.17.y and those all had point
> releases a bunch of people are hitting it now.  If you choose to adopt
> this patch instead of revert the broken one, you can add to the commit
> message too:
>
> Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1976

I am on parental leave kind of, but Bartosz knows what to do,
in this case, since it is ACPI-related, Andy knows best what
to do, and I see he also replied.

Yours,
Linus Walleij

  parent reply	other threads:[~2022-04-19 22:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  2:57 [PATCH] gpio: Request interrupts after IRQ is initialized Mario Limonciello
2022-04-14 15:25 ` Andy Shevchenko
2022-04-14 19:11 ` Shreeya Patel
2022-04-17 12:17 ` luke
2022-04-17 12:24 ` firew4lker
2022-04-18  4:34   ` Mario Limonciello
2022-04-18 11:42     ` Andy Shevchenko
2022-04-18 13:58       ` Thorsten Leemhuis
2022-04-18 14:17         ` Andy Shevchenko
2022-04-18 15:29           ` Thorsten Leemhuis
2022-04-19 13:03     ` Limonciello, Mario
2022-04-19 22:02     ` Linus Walleij [this message]
2022-04-21 16:07       ` Thorsten Leemhuis
2022-04-22 12:18         ` Thorsten Leemhuis
2022-04-22 13:15           ` Limonciello, Mario
2022-04-18 13:46 ` Thorsten Leemhuis
2022-04-19  9:40 ` Samuel Čavoj
2022-04-19 21:59 ` 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='CACRpkdbvN0ZJnn+N=Vt2n_aO4CnM=E4qpe_3dmu-c8_Ufp8ZzQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=Richard.Gong@amd.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=brgl@bgdev.pl \
    --cc=firew4lker@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=shreeya.patel@collabora.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 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.