From: Conor Dooley <conor@kernel.org>
To: palmer@dabbelt.com
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org,
corbet@lwn.net, kernel test robot <lkp@intel.com>
Subject: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Sun, 29 Jan 2023 23:57:01 +0000 [thread overview]
Message-ID: <20230129235701.2393241-1-conor@kernel.org> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
When adding the ISA string ordering rules, I didn't sufficiently indent
one of the list items.
Reported-by: kernel test robot <lkp@intel.com>
Fixes: f07b2b3f9d47 ("Documentation: riscv: add a section about ISA string ordering in /proc/cpuinfo")
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
Documentation/riscv/uabi.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/riscv/uabi.rst b/Documentation/riscv/uabi.rst
index 2ebec4c52230..8960fac42c40 100644
--- a/Documentation/riscv/uabi.rst
+++ b/Documentation/riscv/uabi.rst
@@ -21,10 +21,10 @@ so for our purposes the following rules apply:
single-letter extensions and before any higher-privileged extensions.
#. For additional standard extensions, the first letter following the 'Z'
- conventionally indicates the most closely related alphabetical
- extension category. If multiple 'Z' extensions are named, they will be ordered
- first by category, in canonical order, as listed above, then alphabetically
- within a category.
+ conventionally indicates the most closely related alphabetical
+ extension category. If multiple 'Z' extensions are named, they will be
+ ordered first by category, in canonical order, as listed above, then
+ alphabetically within a category.
#. Standard supervisor-level extensions (starting with 'S') will be listed
after standard unprivileged extensions. If multiple supervisor-level
--
2.39.1
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor@kernel.org>
To: palmer@dabbelt.com
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org,
corbet@lwn.net, kernel test robot <lkp@intel.com>
Subject: [PATCH] Documentation: riscv: fix insufficient list item indent
Date: Sun, 29 Jan 2023 23:57:01 +0000 [thread overview]
Message-ID: <20230129235701.2393241-1-conor@kernel.org> (raw)
From: Conor Dooley <conor.dooley@microchip.com>
When adding the ISA string ordering rules, I didn't sufficiently indent
one of the list items.
Reported-by: kernel test robot <lkp@intel.com>
Fixes: f07b2b3f9d47 ("Documentation: riscv: add a section about ISA string ordering in /proc/cpuinfo")
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
Documentation/riscv/uabi.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/riscv/uabi.rst b/Documentation/riscv/uabi.rst
index 2ebec4c52230..8960fac42c40 100644
--- a/Documentation/riscv/uabi.rst
+++ b/Documentation/riscv/uabi.rst
@@ -21,10 +21,10 @@ so for our purposes the following rules apply:
single-letter extensions and before any higher-privileged extensions.
#. For additional standard extensions, the first letter following the 'Z'
- conventionally indicates the most closely related alphabetical
- extension category. If multiple 'Z' extensions are named, they will be ordered
- first by category, in canonical order, as listed above, then alphabetically
- within a category.
+ conventionally indicates the most closely related alphabetical
+ extension category. If multiple 'Z' extensions are named, they will be
+ ordered first by category, in canonical order, as listed above, then
+ alphabetically within a category.
#. Standard supervisor-level extensions (starting with 'S') will be listed
after standard unprivileged extensions. If multiple supervisor-level
--
2.39.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-01-29 23:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 23:57 Conor Dooley [this message]
2023-01-29 23:57 ` [PATCH] Documentation: riscv: fix insufficient list item indent Conor Dooley
2023-01-30 3:05 ` Bagas Sanjaya
2023-01-30 3:05 ` Bagas Sanjaya
2023-01-31 19:18 ` Conor Dooley
2023-01-31 19:18 ` Conor Dooley
2023-02-09 18:48 ` Palmer Dabbelt
2023-02-09 18:48 ` Palmer Dabbelt
2023-02-09 19:23 ` Conor Dooley
2023-02-09 19:23 ` Conor Dooley
2023-02-07 14:58 ` Conor Dooley
2023-02-07 14:58 ` Conor Dooley
2023-02-09 18:48 ` Palmer Dabbelt
2023-02-09 18:48 ` Palmer Dabbelt
2023-02-09 18:44 ` Palmer Dabbelt
2023-02-09 18:44 ` Palmer Dabbelt
2023-02-15 15:00 ` patchwork-bot+linux-riscv
2023-02-15 15:00 ` patchwork-bot+linux-riscv
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=20230129235701.2393241-1-conor@kernel.org \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lkp@intel.com \
--cc=palmer@dabbelt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.