From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Dave Martin <Dave.Martin@arm.com>,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Edmund Grimley-Evans <edmund.grimley-evans@arm.com>
Subject: [PATCH v2 0/4] arm64/fp: Documentation cleanups and clarifications
Date: Wed, 24 Jan 2024 18:12:34 +0000 [thread overview]
Message-ID: <20240124-arm64-sve-sme-doc-v2-0-fe3964fb3c19@kernel.org> (raw)
Edwin noticed some issues with the SVE and SME documentation which are
corrected by this series.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Changes in v2:
- Explicitly say which prtcl() configures the vector length.
- Link to v1: https://lore.kernel.org/r/20240122-arm64-sve-sme-doc-v1-0-3d492e45265b@kernel.org
---
Mark Brown (4):
arm64/sve: Remove bitrotted comment about syscall behaviour
arm64/sme: Fix cut'n'paste in ABI document
arm64/fp: Clarify effect of setting an unsupported system VL
arm64/sme: Remove spurious 'is' in SME documentation
Documentation/arch/arm64/sme.rst | 11 +++++------
Documentation/arch/arm64/sve.rst | 10 ++--------
2 files changed, 7 insertions(+), 14 deletions(-)
---
base-commit: 6613476e225e090cc9aad49be7fa504e290dd33d
change-id: 20240110-arm64-sve-sme-doc-bc62ec1a2005
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2024-01-24 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 18:12 Mark Brown [this message]
2024-01-24 18:12 ` [PATCH v2 1/4] arm64/sve: Remove bitrotted comment about syscall behaviour Mark Brown
2024-01-24 18:12 ` [PATCH v2 2/4] arm64/sme: Fix cut'n'paste in ABI document Mark Brown
2024-01-25 13:49 ` Dave Martin
2024-01-24 18:12 ` [PATCH v2 3/4] arm64/fp: Clarify effect of setting an unsupported system VL Mark Brown
2024-01-25 13:47 ` Dave Martin
2024-01-24 18:12 ` [PATCH v2 4/4] arm64/sme: Remove spurious 'is' in SME documentation Mark Brown
2024-02-21 18:24 ` [PATCH v2 0/4] arm64/fp: Documentation cleanups and clarifications Catalin Marinas
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=20240124-arm64-sve-sme-doc-v2-0-fe3964fb3c19@kernel.org \
--to=broonie@kernel.org \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=edmund.grimley-evans@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.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
all inboxes | Powered by JetHome®