From: Catalin Marinas <catalin.marinas@arm.com>
To: Dave Martin <Dave.Martin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, gdb@sourceware.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Will Deacon" <will.deacon@arm.com>,
"Julien Grall" <julien.grall@arm.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Zhang Lei" <zhang.lei@jp.fujitsu.com>,
"Alan Hayward" <alan.hayward@arm.com>
Subject: Re: [PATCH v2 3/3] arm64/sve: Fix a couple of magic numbers for the Z-reg count
Date: Mon, 22 Jul 2019 10:32:00 -0000 [thread overview]
Message-ID: <20190722103200.GB60625@arrakis.emea.arm.com> (raw)
In-Reply-To: <1560355234-25516-4-git-send-email-Dave.Martin@arm.com>
On Wed, Jun 12, 2019 at 05:00:34PM +0100, Dave P Martin wrote:
> There are some hand-written instances of "32" to express the number
> of SVE Z-registers.
>
> Since this code was written a #define was added for this, so
> convert trivial instances of this magic number as appropriate.
>
> No functional change.
>
> Signed-off-by: Dave Martin <Dave.Martin@arm.com>
Same here, Will can queue this for -rc2.
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
next prev parent reply other threads:[~2019-07-22 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 16:00 [PATCH v2 0/3] arm64/sve: Fix mutating register endianness on big-endian Dave Martin
2019-06-12 16:01 ` [PATCH v2 3/3] arm64/sve: Fix a couple of magic numbers for the Z-reg count Dave Martin
2019-06-20 13:43 ` Julien Grall
2019-07-22 10:32 ` Catalin Marinas [this message]
2019-06-12 16:01 ` [PATCH v2 2/3] arm64/sve: Factor out FPSIMD to SVE state conversion Dave Martin
2019-06-20 13:45 ` Julien Grall
2019-07-22 10:31 ` Catalin Marinas
2019-06-12 16:01 ` [PATCH v2 1/3] arm64/sve: Fix missing SVE/FPSIMD endianness conversions Dave Martin
2019-06-12 17:29 ` Will Deacon
[not found] ` <20190627135112.GC9894@arrakis.emea.arm.com>
2019-06-27 15:18 ` Dave Martin
2019-06-12 17:46 ` Julien Grall
2019-06-13 9:22 ` Will Deacon
2019-06-13 10:00 ` Dave Martin
2019-06-13 10:17 ` Will Deacon
2019-06-13 10:20 ` Dave Martin
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=20190722103200.GB60625@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=Dave.Martin@arm.com \
--cc=alan.hayward@arm.com \
--cc=alex.bennee@linaro.org \
--cc=gdb@sourceware.org \
--cc=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peter.maydell@linaro.org \
--cc=will.deacon@arm.com \
--cc=zhang.lei@jp.fujitsu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).