Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 13:30:25 +0000	[thread overview]
Message-ID: <1be1b5e9-9aa9-4f1c-9cdc-c4bf94f2dbc8@sirena.org.uk> (raw)
In-Reply-To: <Z6tNiIMIhN5fPSJM@J2N7QTR9R3>

[-- Attachment #1: Type: text/plain, Size: 859 bytes --]

On Tue, Feb 11, 2025 at 01:15:52PM +0000, Mark Rutland wrote:
> On Tue, Feb 11, 2025 at 12:58:10PM +0000, Mark Brown wrote:

> > 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.

> It would be simpler for others if you sent a single patch that handled
> the three hwcaps that we failed to wire up in commit 819935464cb2. That
> way they only have one thing to track.

> I don't understand what you mean by "two different changelogs"; surely the
> commit message is a trivial variation of the one for this v1 patch:

My first scan through had made it look like there was more stuff missing
for FPRCVT but now that I go to write the change that's not actually the
case, it's different handling of the different ID registers.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 484 bytes --]

      reply	other threads:[~2025-02-11 13:40 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
2025-02-11 13:15         ` Mark Rutland
2025-02-11 13:30           ` Mark Brown [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=1be1b5e9-9aa9-4f1c-9cdc-c4bf94f2dbc8@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