From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Eric Schikschneit <eric.schikschneit@novatechautomation.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>,
"tony@atomide.com" <tony@atomide.com>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>
Subject: Re: [REGRESSION] gpio: omap: ensure irq is enabled before wakeup
Date: Wed, 8 Jun 2022 10:19:01 +0100 [thread overview]
Message-ID: <YqBphR1XTcqqbvG9@shell.armlinux.org.uk> (raw)
In-Reply-To: <2725aaed-6c31-2cce-dcd2-55f2f1ed533c@leemhuis.info>
On Wed, Jun 08, 2022 at 10:54:48AM +0200, Thorsten Leemhuis wrote:
> On 07.06.22 13:58, Eric Schikschneit wrote:
> > I am limited by the availability of the preempt-rt kernels that are
> > available on the yocto project. The newest kernel I see listed is
> > 5.15.44 on: https://git.yoctoproject.org/linux-yocto/
>
> Well, it's up to Russel if that is enough for him, as he authored
> c859e0d479b3 ("gpio: omap: ensure irq is enabled before wakeup") and
> thus should look into this regression.
I've already made it clear that is something I can no longer do; I
no longer have the knowledge, nor do I have the hardware to test
for this regression.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-06-08 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:56 [REGRESSION] gpio: omap: ensure irq is enabled before wakeup Eric Schikschneit
2022-06-07 10:07 ` Thorsten Leemhuis
2022-06-07 11:58 ` Eric Schikschneit
2022-06-08 8:54 ` Thorsten Leemhuis
2022-06-08 9:19 ` Russell King (Oracle) [this message]
2022-06-08 11:08 ` Russell King (Oracle)
2022-06-08 11:28 ` [REGRESSION] gpio: omap: ensure irq is enabled before wakeup #forregzbot Thorsten Leemhuis
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=YqBphR1XTcqqbvG9@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=eric.schikschneit@novatechautomation.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=tony@atomide.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.