Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: Add missing registrations of SF8MMx hwcaps
Date: Tue, 11 Feb 2025 11:37:44 +0000	[thread overview]
Message-ID: <Z6s2iMP1LbdsYX12@J2N7QTR9R3> (raw)
In-Reply-To: <dae7f7b2-f066-4adc-974b-54649ba69306@sirena.org.uk>

On Mon, Feb 10, 2025 at 07:14:58PM +0000, Mark Brown wrote:
> On Mon, Feb 10, 2025 at 06:41:09PM +0000, Mark Rutland wrote:
> > On Mon, Feb 10, 2025 at 05:49:33PM +0000, Mark Brown wrote:
> > > Commit 819935464cb2 ("arm64/hwcap: Describe 2024 dpISA extensions to
> > > userspace") added definitions for HWCAP_F8MM8 and HWCAP_F8MM4 but did
> > > not include the crucial registration in arm64_elf_hwcaps.  Add it.
> 
> > Looking again, it looks like KERNEL_HWCAP_FPRCVT also isn't wired up?
> 
> Indeed.  I'll add that separately.

Given that KERNEL_HWCAP_FPRCVT was also added by commit 819935464cb2,
I assume you mean you'll send a v2 of this patch doing that.

Mark.


  reply	other threads:[~2025-02-11 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10 17:49 [PATCH] arm64: Add missing registrations of SF8MMx hwcaps Mark Brown
2025-02-10 18:41 ` Mark Rutland
2025-02-10 19:14   ` Mark Brown
2025-02-11 11:37     ` Mark Rutland [this message]
2025-02-11 12:58       ` Mark Brown
2025-02-11 13:15         ` Mark Rutland
2025-02-11 13:30           ` Mark Brown

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=Z6s2iMP1LbdsYX12@J2N7QTR9R3 \
    --to=mark.rutland@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=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