From: Mark Rutland <mark.rutland@arm.com>
To: Mathias Stearn <mathias@mongodb.com>
Cc: Will Deacon <will@kernel.org>,
Jinjie Ruan <ruanjinjie@huawei.com>,
linux-arm-kernel@lists.infradead.org,
Catalin Marinas <catalin.marinas@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
ckennelly@google.com, dvyukov@google.com,
linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com
Subject: Re: [PATCHv2] arm64/entry: Fix arm64-specific rseq brokenness
Date: Thu, 18 Jun 2026 16:16:36 +0100 [thread overview]
Message-ID: <ajQL1KII_t4aSmS5@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <ajPv1tew-QAFE1ib@J2N7QTR9R3.cambridge.arm.com>
On Thu, Jun 18, 2026 at 02:17:10PM +0100, Mark Rutland wrote:
> On Thu, Jun 18, 2026 at 09:55:20AM +0200, Mathias Stearn wrote:
> > On Wed, Jun 10, 2026 at 2:37 PM Will Deacon <will@kernel.org> wrote:
> > >
> > > On Tue, Jun 09, 2026 at 02:04:23PM +0200, Mathias Stearn wrote:
> > > > Is it possible to get 411c1cf43039 backported to 7.0 or was it omitted
> > > > intentionally?
> > >
> > > You can send a backport to the stable maintainers:
> > >
> > > https://docs.kernel.org/process/stable-kernel-rules.html#procedure-for-submitting-patches-to-the-stable-tree
> >
> > Who was that "you" directed at? I'm not used to the kernel development
> > process. Is that my responsibility as the bug reporter / interested
> > party, or something that Mark Rutland, author of the patch, should do?
>
> I'll sort it out.
I've send a backport for v7.0; when lore updates it should be visible at:
https://lore.kernel.org/stable/20260618151426.308099-1-mark.rutland@arm.com/
Mark.
prev parent reply other threads:[~2026-06-18 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 14:20 [PATCHv2] arm64/entry: Fix arm64-specific rseq brokenness Mark Rutland
2026-05-08 14:24 ` Catalin Marinas
2026-05-11 3:18 ` Jinjie Ruan
2026-06-09 12:04 ` Mathias Stearn
2026-06-10 12:37 ` Will Deacon
2026-06-18 7:55 ` Mathias Stearn
2026-06-18 13:17 ` Mark Rutland
2026-06-18 15:16 ` Mark Rutland [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=ajQL1KII_t4aSmS5@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=ckennelly@google.com \
--cc=dvyukov@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathias@mongodb.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=tglx@linutronix.de \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox