From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Karl Mehltretter <kmehltretter@gmail.com>,
kernel-team@android.com, Mark Rutland <mark.rutland@arm.com>,
Oleg Nesterov <oleg@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64/fpsimd: ptrace: Fix inactive SVE and SSVE regsets
Date: Thu, 6 Aug 2026 13:20:02 +0100 [thread overview]
Message-ID: <anR78qO5RGalbFNo@willie-the-truck> (raw)
In-Reply-To: <be47f939-bc44-46b8-ba38-988403dd87b0@sirena.org.uk>
On Thu, Aug 06, 2026 at 01:15:25PM +0100, Mark Brown wrote:
> On Thu, Aug 06, 2026 at 11:57:12AM +0100, Will Deacon wrote:
> > On Wed, Aug 05, 2026 at 10:27:18PM +0100, Mark Brown wrote:
>
> > > As noted in the changelog applying patch 1 as a fix and this only for
> > > -next blows up the fp-ptrace test rather impressively in any
> > > configuration which can generate headers only reports:
>
> > > https://lava.sirena.org.uk/scheduler/job/3075737#L3231
>
> > > for the release. Both patches really do need to go together.
>
> > By "blows up" you mean the test fails, right? That's the same behaviour
> > if anybody runs the test on a kernel without the fix. Both patches are
> > merged in for-next/core.
>
> Right, the test starts reporting 96 fails which doesn't look great in a
> dashboard. I'd misread the original branch as being merged as a fix but
> I see it's not been merged into the fixes branch, sorry for the
> confusion.
No problem, thank you for running the tests :)
Will
next prev parent reply other threads:[~2026-08-06 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 0:42 [PATCH 1/2] arm64/fpsimd: ptrace: Fix inactive SVE and SSVE regsets Karl Mehltretter
2026-07-29 0:42 ` [PATCH 2/2] kselftest/arm64: fp-ptrace: Fix checks for " Karl Mehltretter
2026-08-02 12:12 ` [PATCH 1/2] arm64/fpsimd: ptrace: Fix " Will Deacon
2026-08-05 21:27 ` Mark Brown
2026-08-06 10:57 ` Will Deacon
2026-08-06 12:15 ` Mark Brown
2026-08-06 12:20 ` Will Deacon [this message]
2026-08-02 12:12 ` Will Deacon
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=anR78qO5RGalbFNo@willie-the-truck \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=kmehltretter@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oleg@redhat.com \
--cc=shuah@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.