From: Bagas Sanjaya <bagasdotme@gmail.com>
To: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>,
Jonathan Corbet <corbet@lwn.net>, Martin Liska <mliska@suse.cz>,
Andi Kleen <ak@linux.intel.com>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kbuild@vger.kernel.org,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: [PATCH 2/4] Documentation: lto: use bullet list for FAQ
Date: Sat, 16 Jul 2022 16:32:48 +0700 [thread overview]
Message-ID: <20220716093249.19326-3-bagasdotme@gmail.com> (raw)
In-Reply-To: <20220716093249.19326-1-bagasdotme@gmail.com>
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@gmail.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
next prev parent reply other threads:[~2022-07-16 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 9:32 [PATCH 0/4] kbuild: lto: documentation fixes Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 1/4] Documentation: lto: add blank line padding before single requirement list Bagas Sanjaya
2022-07-16 9:32 ` Bagas Sanjaya [this message]
2022-07-16 9:32 ` [PATCH 3/4] Documentation: lto: use bullet lists for external link references list Bagas Sanjaya
2022-07-16 9:32 ` [PATCH 4/4] Documentation: lto: add LTO documentation to toc index Bagas Sanjaya
2022-07-18 1:49 ` [PATCH 0/4] kbuild: lto: documentation fixes Masahiro Yamada
2022-07-18 7:17 ` Bagas Sanjaya
2022-07-19 7:29 ` Jiri Slaby
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=20220716093249.19326-3-bagasdotme@gmail.com \
--to=bagasdotme@gmail.com \
--cc=ak@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jirislaby@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mliska@suse.cz \
--cc=ndesaulniers@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox