From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Yue Haibing <yuehaibing@huawei.com>,
catalin.marinas@arm.com, will@kernel.org, broonie@kernel.org,
mark.rutland@arm.com
Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] arm64/sve: Remove unused declaration read_smcr_features()
Date: Tue, 13 Aug 2024 09:27:06 +0530 [thread overview]
Message-ID: <0f4b602d-90d3-4035-a0e1-0fb061868764@arm.com> (raw)
In-Reply-To: <20240810093944.2587809-1-yuehaibing@huawei.com>
On 8/10/24 15:09, Yue Haibing wrote:
> Commit 391208485c3a ("arm64/sve: Remove SMCR pseudo register from cpufeature code")
> removed the implementation but leave declaration.
>
> Signed-off-by: Yue Haibing <yuehaibing@huawei.com>
> ---
> arch/arm64/include/asm/fpsimd.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/arch/arm64/include/asm/fpsimd.h b/arch/arm64/include/asm/fpsimd.h
> index bc69ac368d73..f2a84efc3618 100644
> --- a/arch/arm64/include/asm/fpsimd.h
> +++ b/arch/arm64/include/asm/fpsimd.h
> @@ -155,8 +155,6 @@ extern void cpu_enable_sme2(const struct arm64_cpu_capabilities *__unused);
> extern void cpu_enable_fa64(const struct arm64_cpu_capabilities *__unused);
> extern void cpu_enable_fpmr(const struct arm64_cpu_capabilities *__unused);
>
> -extern u64 read_smcr_features(void);
> -
> /*
> * Helpers to translate bit indices in sve_vq_map to VQ values (and
> * vice versa). This allows find_next_bit() to be used to find the
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
next prev parent reply other threads:[~2024-08-13 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-10 9:39 Yue Haibing
2024-08-13 3:57 ` Anshuman Khandual [this message]
2024-08-13 10:03 ` Mark Brown
2024-08-14 8:47 ` Zenghui Yu
2024-08-16 15:16 ` 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=0f4b602d-90d3-4035-a0e1-0fb061868764@arm.com \
--to=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
--cc=yuehaibing@huawei.com \
/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
all inboxes | Powered by JetHome®