From: Sasha Levin <sashal@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: stable@vger.kernel.org, gregkh@linuxfoundation.org,
ard.biesheuvel@linaro.org, catalin.marinas@arm.com,
mark.rutland@arm.com, maz@kernel.org,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [stable 4.14 PATCH 1/3] arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly
Date: Sat, 15 Feb 2020 15:23:19 -0500 [thread overview]
Message-ID: <20200215202319.GI1734@sasha-vm> (raw)
In-Reply-To: <20200214151937.1950083-1-suzuki.poulose@arm.com>
On Fri, Feb 14, 2020 at 03:19:35PM +0000, Suzuki K Poulose wrote:
>commit 7ef1ab8792c50797c6c5c7c5150a02460 upstream
>
>We set the compat_elf_hwcap bits unconditionally on arm64 to
>include the VFP and NEON support. However, the FP/SIMD unit
>is optional on Arm v8 and thus could be missing. We already
>handle this properly in the kernel, but still advertise to
>the COMPAT applications that the VFP is available. Fix this
>to make sure we only advertise when we really have them.
>
>Cc: stable@vger.kernel.org # v4.14
>Cc: Will Deacon <will@kernel.org>
>Cc: Mark Rutland <mark.rutland@arm.com>
>Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
>Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
>Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Queued for 4.14, thank you.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-02-15 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 15:19 [stable 4.14 PATCH 1/3] arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly Suzuki K Poulose
2020-02-14 15:19 ` [stable 4.14 PATCH 2/3] arm64: ptrace: nofpsimd: Fail FP/SIMD regset operations Suzuki K Poulose
2020-02-14 15:19 ` [stable 4.14 PATCH 3/3] arm64: nofpsimd: Handle TIF_FOREIGN_FPSTATE flag cleanly Suzuki K Poulose
2020-02-15 20:23 ` Sasha Levin [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=20200215202319.GI1734@sasha-vm \
--to=sashal@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).