From: "Martin Liška" <mliska@suse.cz>
To: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Cc: broonie@kernel.org, corbet@lwn.net, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] docs/arm64: elf_hwcaps: unify newlines in HWCAP lists
Date: Mon, 15 Aug 2022 15:37:58 +0200 [thread overview]
Message-ID: <2bac83ef-d5a9-b8c4-0fb3-cef4272e7156@suse.cz> (raw)
In-Reply-To: <49253b17-738d-795e-f539-55857fdaee64@suse.cz>
In git revision 94bdaa7d9a9d778d893c670d494c06d8e007c1cd I unified
vertical spaces in a list of features.
Since the revision, another commits added new features that have a different
horizontal spacing.
Fix these extra newlines.
Signed-off-by: Martin Liska <mliska@suse.cz>
---
Documentation/arm64/elf_hwcaps.rst | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/Documentation/arm64/elf_hwcaps.rst b/Documentation/arm64/elf_hwcaps.rst
index 52b75a25c205..311021f2e560 100644
--- a/Documentation/arm64/elf_hwcaps.rst
+++ b/Documentation/arm64/elf_hwcaps.rst
@@ -242,44 +242,34 @@ HWCAP2_MTE3
by Documentation/arm64/memory-tagging-extension.rst.
HWCAP2_SME
-
Functionality implied by ID_AA64PFR1_EL1.SME == 0b0001, as described
by Documentation/arm64/sme.rst.
HWCAP2_SME_I16I64
-
Functionality implied by ID_AA64SMFR0_EL1.I16I64 == 0b1111.
HWCAP2_SME_F64F64
-
Functionality implied by ID_AA64SMFR0_EL1.F64F64 == 0b1.
HWCAP2_SME_I8I32
-
Functionality implied by ID_AA64SMFR0_EL1.I8I32 == 0b1111.
HWCAP2_SME_F16F32
-
Functionality implied by ID_AA64SMFR0_EL1.F16F32 == 0b1.
HWCAP2_SME_B16F32
-
Functionality implied by ID_AA64SMFR0_EL1.B16F32 == 0b1.
HWCAP2_SME_F32F32
-
Functionality implied by ID_AA64SMFR0_EL1.F32F32 == 0b1.
HWCAP2_SME_FA64
-
Functionality implied by ID_AA64SMFR0_EL1.FA64 == 0b1.
HWCAP2_WFXT
-
Functionality implied by ID_AA64ISAR2_EL1.WFXT == 0b0010.
HWCAP2_EBF16
-
Functionality implied by ID_AA64ISAR1_EL1.BF16 == 0b0010.
4. Unused AT_HWCAP bits
--
2.37.1
next prev parent reply other threads:[~2022-08-15 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 9:19 [PATCH] docs/arm64: elf_hwcaps: Unify HWCAP lists as description lists Martin Liška
2022-08-15 13:00 ` Mark Brown
2022-08-15 13:37 ` Martin Liška [this message]
2022-08-18 17:17 ` [PATCH v2] docs/arm64: elf_hwcaps: unify newlines in HWCAP lists Mark Brown
2022-08-18 20:31 ` [PATCH v3] " Martin Liška
2022-08-23 11:34 ` Will Deacon
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=2bac83ef-d5a9-b8c4-0fb3-cef4272e7156@suse.cz \
--to=mliska@suse.cz \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.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®