From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: stable@vger.kernel.org, Bryan Brattlof <bb@ti.com>,
Daniel Wagner <daniel.wagner@monom.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
cip-dev@lists.cip-project.org,
nobuhiro.iwamatsu.x90@mail.toshiba, pavel@nabladev.com,
Russell King <rmk+kernel@armlinux.org.uk>
Subject: Re: [PATCH 0/4] ARM: stable backports
Date: Mon, 8 Jun 2026 16:12:05 +0200 [thread overview]
Message-ID: <2026060832-extortion-cattail-2467@gregkh> (raw)
In-Reply-To: <20260608082818.LZiPJ9ot@linutronix.de>
On Mon, Jun 08, 2026 at 10:28:18AM +0200, Sebastian Andrzej Siewior wrote:
> On 2026-05-11 15:53:53 [+0200], To stable@vger.kernel.org wrote:
> > This is a backport of ARM related fixes. This applies cleanly to v6.18
> > and v6.12. I have an updated batch for v6.6 and v6.1 because this does
> > not apply cleanly.
> >
> > #1 and #2 are prerequisites for #3.
> >
> > Can't tell the origin of #3 (fix hash_name() fault). It might be there
> > since the begin of time.
> >
> > #4 (fix branch predictor hardening) fixes commit f5fe12b1eaee2 ("ARM:
> > spectre-v2: harden user aborts in kernel space") which is v4.20-rc2.
> >
> > If there are no objections I would post the v6.6 version once this is
> > accepted and then rebase the PREEMPT_RT bits on top of this.
>
> I noticed that the ARM64 patches I sent recently were picked up and
> backported but this is still waiting.
>
> I there something I can do to speed things up?
We have hundreds of patches in the backlog right now, these are way down
the list, sorry. Hope to catch up "soon"...
thanks,
greg k-h
prev parent reply other threads:[~2026-06-08 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 13:53 [PATCH 0/4] ARM: stable backports Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 1/4] ARM: group is_permission_fault() with is_translation_fault() Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 2/4] ARM: allow __do_kernel_fault() to report execution of memory faults Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 3/4] ARM: fix hash_name() fault Sebastian Andrzej Siewior
2026-05-11 13:53 ` [PATCH 4/4] ARM: fix branch predictor hardening Sebastian Andrzej Siewior
2026-05-12 8:00 ` [PATCH 0/4] ARM: stable backports Pavel Machek
2026-05-13 13:51 ` Bryan Brattlof
2026-06-08 8:28 ` Sebastian Andrzej Siewior
2026-06-08 14:12 ` Greg KH [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=2026060832-extortion-cattail-2467@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bb@ti.com \
--cc=bigeasy@linutronix.de \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.wagner@monom.org \
--cc=jan.kiszka@siemens.com \
--cc=nobuhiro.iwamatsu.x90@mail.toshiba \
--cc=pavel@nabladev.com \
--cc=rmk+kernel@armlinux.org.uk \
--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.