Linux-Sparse Archive on lore.kernel.org
 help / color / Atom feed
* [PATCH] doc: fix markup in types.rst (s/```/``/)
@ 2020-06-16 21:04 Luc Van Oostenryck
  0 siblings, 0 replies; only message in thread
From: Luc Van Oostenryck @ 2020-06-16 21:04 UTC (permalink / raw)
  To: linux-sparse; +Cc: Luc Van Oostenryck

Literal text was marked with ``` but that's a bit excessive.

Fix that by replacing these with ``.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 Documentation/types.rst | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/Documentation/types.rst b/Documentation/types.rst
index 5c10725fa71a..272f32a0f4ed 100644
--- a/Documentation/types.rst
+++ b/Documentation/types.rst
@@ -30,16 +30,16 @@ Some bits, also related to the type, are in struct symbol itself:
   * accessed
   * transparent_union
 
-* ```base_type``` is used for the associated base type.
-* ```modifiers``` is a bit mask for type specifiers (MOD_UNSIGNED, ...),
+* ``base_type`` is used for the associated base type.
+* ``modifiers`` is a bit mask for type specifiers (MOD_UNSIGNED, ...),
   type qualifiers (MOD_CONST, MOD_VOLATILE),
   storage classes (MOD_STATIC, MOD_EXTERN, ...), as well for various
   attributes. It's also used internally to keep track of some states
   (MOD_ACCESS or MOD_ADDRESSABLE).
-* ```alignment``` is used for the alignment, in bytes.
-* ```contexts``` is used to store the informations associated with the
-  attribute ```context()```.
-* ```as``` is used to hold the identifier of the attribute ```address_space()```.
+* ``alignment`` is used for the alignment, in bytes.
+* ``contexts`` is used to store the informations associated with the
+  attribute ``context()``.
+* ``as`` is used to hold the identifier of the attribute ``address_space()``.
 
 Kind of types
 =============
@@ -49,11 +49,11 @@ SYM_BASETYPE
 Used by integer, floating-point, void, 'type', 'incomplete' & bad types.
 
 For integer types:
-  * .ctype.base_type points to ```int_ctype```, the generic/abstract integer type
+  * .ctype.base_type points to ``int_ctype``, the generic/abstract integer type
   * .ctype.modifiers has MOD_UNSIGNED/SIGNED/EXPLICITLY_SIGNED set accordingly.
 
 For floating-point types:
-  * .ctype.base_type points to ```fp_ctype```, the generic/abstract float type
+  * .ctype.base_type points to ``fp_ctype``, the generic/abstract float type
   * .ctype.modifiers is zero.
 
 For the other base types:
@@ -131,7 +131,7 @@ Used for bitwise types (aka 'restricted' types):
 SYM_FOULED
 ----------
 Used for bitwise types when the negation op (~) is
-used and the bit_size is smaller than an ```int```.
+used and the bit_size is smaller than an ``int``.
 There is a 1-to-1 mapping between a fouled type and
 its parent bitwise type.
 
-- 
2.27.0

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-16 21:04 [PATCH] doc: fix markup in types.rst (s/```/``/) Luc Van Oostenryck

Linux-Sparse Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-sparse/0 linux-sparse/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-sparse linux-sparse/ https://lore.kernel.org/linux-sparse \
		linux-sparse@vger.kernel.org
	public-inbox-index linux-sparse

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-sparse


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git