linux-kernel - [PATCH 2/4] Documentation: lto: use bullet list for FAQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sat, 16 Jul 2022 16:32:48 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     linux-doc@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org,
        Masahiro Yamada <masahiroy@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Jonathan Corbet <corbet@....net>,
        Martin Liska <mliska@...e.cz>, Andi Kleen <ak@...ux.intel.com>,
        Jiri Slaby <jirislaby@...nel.org>,
        linux-kbuild@...r.kernel.org, Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH 2/4] Documentation: lto: use bullet list for FAQ

The only FAQ item is rendered as a continuous paragraph, although it is
formatted as Q&A field pair. Use bullet list instead, as in other FAQs
in kernel documentation.

Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
 Documentation/kbuild/lto-build.rst | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/Documentation/kbuild/lto-build.rst b/Documentation/kbuild/lto-build.rst
index 39cbdb12295051..9e3e14042dda4c 100644
--- a/Documentation/kbuild/lto-build.rst
+++ b/Documentation/kbuild/lto-build.rst
@@ -46,10 +46,12 @@ You can however build a kernel targeted at 32bit on a 64bit host.
 
 FAQs:
 -----
-Q: I get a section type attribute conflict
-A: Usually because of someone doing
-const __initdata (should be const __initconst) or const __read_mostly
-(should be just const). Check both symbols reported by gcc.
+
+* I get a section type attribute conflict
+
+  Usually because of someone doing const __initdata (should be
+  const __initconst) or const __read_mostly (should be just const). Check
+  both symbols reported by gcc.
 
 References:
 -----------
-- 
An old man doll... just what I always wanted! - Clara