On Wed, Nov 30, 2022 at 11:41:26PM +0000, Conor Dooley wrote:
> +#. Single-letter extensions come first, in "canonical order", so
> + "IMAFDQLCBKJTPVH".
"..., that is ... ."
> +#. The first letter following the 'Z' conventionally indicates the most
> + closely related alphabetical extension category, IMAFDQLCBKJTPVH.
> + If multiple 'Z' extensions are named, they should be ordered first by
> + category, then alphabetically within a category.
> +
Did you mean "most closely related alphabetical extension category in
canonical order"?
> +An example string following the order is:
> + rv64imadc_zifoo_zigoo_zafoo_sbar_scar_zxmbaz_xqux_xrux
> +
IMO literal code block should be better fit for the example above,
rather than definition list:
---- >8 ----
diff --git a/Documentation/riscv/uabi.rst b/Documentation/riscv/uabi.rst
index bc3c8ced644bcf..8005add855dc43 100644
--- a/Documentation/riscv/uabi.rst
+++ b/Documentation/riscv/uabi.rst
@@ -43,6 +43,7 @@ ordering, so for our purposes the following rules apply:
#. Non-standard extensions (starts with 'X') will be listed after all
standard extensions.
-An example string following the order is:
+An example string following the order is::
+
rv64imadc_zifoo_zigoo_zafoo_sbar_scar_zxmbaz_xqux_xrux
Thanks.
--
An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature
