From: Mark Brown <broonie@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
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 12:58:10 +0000 [thread overview]
Message-ID: <bec2a37a-1797-41d2-a44a-a34a54a96f89@sirena.org.uk> (raw)
In-Reply-To: <Z6s2iMP1LbdsYX12@J2N7QTR9R3>
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
On Tue, Feb 11, 2025 at 11:37:44AM +0000, Mark Rutland wrote:
> 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:
> > > 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.
Well, I was actually intending to send a separate patch given that
otherwise it ends up looking like two different changelogs in the same
patch and the diffs shouldn't overlap.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-02-11 13:17 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
2025-02-11 12:58 ` Mark Brown [this message]
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=bec2a37a-1797-41d2-a44a-a34a54a96f89@sirena.org.uk \
--to=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 \
/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