From: Will Deacon <will@kernel.org>
To: Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] arm64/sme: Fixes for SME only support
Date: Thu, 5 Jan 2023 18:03:55 +0000 [thread overview]
Message-ID: <167293268011.1467456.7524562556559466866.b4-ty@kernel.org> (raw)
In-Reply-To: <20221223-arm64-fix-sme-only-v1-0-938d663f69e5@kernel.org>
On Tue, 27 Dec 2022 17:12:04 +0000, Mark Brown wrote:
> There is no architectural requirement for systems implementing SME to
> also implement SVE, though it is expected to be an unusual configuration.
> This series fixes several cases where such systems would encounter
> problems, one introduced in the refactoring to avoid disabling SVE over
> system call and the other two in signal handling which have been there
> since SME was initially supported.
>
> [...]
Applied to arm64 (for-next/fixes), thanks!
[1/3] arm64/sme: Fix context switch for SME only systems
https://git.kernel.org/arm64/c/0cab5b4964c7
[2/3] arm64/signal: Always accept SVE signal frames on SME only systems
https://git.kernel.org/arm64/c/7dde62f0687c
[3/3] arm64/signal: Always allocate SVE signal frames on SME only systems
https://git.kernel.org/arm64/c/f26cd7372160
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-01-05 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 17:12 [PATCH 0/3] arm64/sme: Fixes for SME only support Mark Brown
2022-12-27 17:12 ` [PATCH 1/3] arm64/sme: Fix context switch for SME only systems Mark Brown
2022-12-27 17:12 ` [PATCH 2/3] arm64/signal: Always accept SVE signal frames on " Mark Brown
2022-12-27 17:12 ` [PATCH 3/3] arm64/signal: Always allocate " Mark Brown
2023-01-05 15:22 ` [PATCH 0/3] arm64/sme: Fixes for SME only support Will Deacon
2023-01-05 15:29 ` Will Deacon
2023-01-05 16:00 ` Mark Brown
2023-01-05 15:47 ` Mark Brown
2023-01-05 18:03 ` Will Deacon [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=167293268011.1467456.7524562556559466866.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).