From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Pierre Gondois <pierre.gondois@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
stable-rt@vger.kernel.org
Subject: Re: [ANNOUNCE] v6.0.5-rt14
Date: Mon, 31 Oct 2022 14:26:44 +0100 [thread overview]
Message-ID: <Y1/NFIjRFZzszZB6@linutronix.de> (raw)
In-Reply-To: <649af0f6-e5e2-c450-879c-e9153e0c0abc@arm.com>
On 2022-10-28 11:47:28 [+0200], Pierre Gondois wrote:
> Hello Sebastian,
Hi Pierre,
> About the issues Valentin reported:
>
> - [SPLAT 1/3] arm_pmu: Sleeping spinlocks down armpmu_alloc_atomic()
> will be fixed by:
> https://lore.kernel.org/all/20220930111844.1522365-1-mark.rutland@arm.com/
This is still pending and I don't see it in next. Could someone give me
a ping once this is merged, please?
> - [SPLAT 2/3] irqchip/gic-v3-its: Sleeping spinlocks down gic_reserve_range()
> was fixed by:
> https://lore.kernel.org/lkml/20211027151506.2085066-3-valentin.schneider@arm.com/
That is
d23bc2bc1d634 ("irqchip/gic-v3-its: Postpone LPI pending table freeing and memreserve")
v5.17-rc1
> - [SPLAT 3/3] gpio: dwapb: Sleeping spinlocks down IRQ mapping
> was fixed by:
> https://lore.kernel.org/all/20220419012810.88417-1-schspa@gmail.com/
3c938cc5cebcb ("gpio: use raw spinlock for gpio chip shadowed data")
v5.19-rc1
Is someone picking the two up or RT-stable?
> Regards,
> Pierre
Sebastian
next prev parent reply other threads:[~2022-10-31 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 8:08 [ANNOUNCE] v6.0.5-rt14 Sebastian Andrzej Siewior
2022-10-28 9:47 ` Pierre Gondois
2022-10-31 13:26 ` Sebastian Andrzej Siewior [this message]
2022-10-31 14:06 ` Clark Williams
2022-12-13 13:56 ` Pierre Gondois
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=Y1/NFIjRFZzszZB6@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pierre.gondois@arm.com \
--cc=rostedt@goodmis.org \
--cc=stable-rt@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox