From: Dave Martin <Dave.Martin@arm.com>
To: Julien Grall <julien.grall@arm.com>
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Documentation/arm64/sve: Couple of improvements and typoes
Date: Fri, 31 Aug 2018 12:03:57 +0100 [thread overview]
Message-ID: <20180831110347.GA17801@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20180814103332.28836-1-julien.grall@arm.com>
On Tue, Aug 14, 2018 at 11:33:32AM +0100, Julien Grall wrote:
> - Fix mismatch between SVE registers (Z) and FPSIMD register (V)
> - Don't prefix the path for [3] with Linux to stay consistent with
> [1] and [2].
>
> Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Dave Martin <Dave.Martin@arm.com>
(in case nobody picked this up yet).
Cheers
---Dave
> ---
> Documentation/arm64/sve.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/arm64/sve.txt b/Documentation/arm64/sve.txt
> index f128f736b4a5..7169a0ec41d8 100644
> --- a/Documentation/arm64/sve.txt
> +++ b/Documentation/arm64/sve.txt
> @@ -200,7 +200,7 @@ prctl(PR_SVE_SET_VL, unsigned long arg)
> thread.
>
> * Changing the vector length causes all of P0..P15, FFR and all bits of
> - Z0..V31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
> + Z0..Z31 except for Z0 bits [127:0] .. Z31 bits [127:0] to become
> unspecified. Calling PR_SVE_SET_VL with vl equal to the thread's current
> vector length, or calling PR_SVE_SET_VL with the PR_SVE_SET_VL_ONEXEC
> flag, does not constitute a change to the vector length for this purpose.
> @@ -500,7 +500,7 @@ References
> [2] arch/arm64/include/uapi/asm/ptrace.h
> AArch64 Linux ptrace ABI definitions
>
> -[3] linux/Documentation/arm64/cpu-feature-registers.txt
> +[3] Documentation/arm64/cpu-feature-registers.txt
>
> [4] ARM IHI0055C
> http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055c/IHI0055C_beta_aapcs64.pdf
> --
> 2.11.0
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2018-08-31 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 10:33 Julien Grall
2018-08-31 11:03 ` Dave Martin [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=20180831110347.GA17801@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=julien.grall@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.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®