From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Thorsten Leemhuis <linux@leemhuis.info>,
Kees Cook <keescook@chromium.org>,
Jani Nikula <jani.nikula@linux.intel.com>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v2 5/7] docs: move asm-annotations.rst into core-api
Date: Fri, 23 Sep 2022 14:45:34 +0700 [thread overview]
Message-ID: <Yy1kHrS7ieq1VCqw@debian.me> (raw)
In-Reply-To: <20220922204138.153146-6-corbet@lwn.net>
[-- Attachment #1: Type: text/plain, Size: 2785 bytes --]
On Thu, Sep 22, 2022 at 02:41:36PM -0600, Jonathan Corbet wrote:
> @@ -43,10 +43,11 @@ annotated objects like this, tools can be run on them to generate more useful
> information. In particular, on properly annotated objects, ``objtool`` can be
> run to check and fix the object if needed. Currently, ``objtool`` can report
> missing frame pointer setup/destruction in functions. It can also
> -automatically generate annotations for :doc:`ORC unwinder <x86/orc-unwinder>`
> +automatically generate annotations for the ORC unwinder
> +(Documentation/x86/orc-unwinder.rst)
> for most code. Both of these are especially important to support reliable
> -stack traces which are in turn necessary for :doc:`Kernel live patching
> -<livepatch/livepatch>`.
> +stack traces which are in turn necessary for kernel live patching
> +(Documentation/livepatch/livepatch.rst).
Hi jon,
I think Sphinx internal references are better fit for these links:
---- >8 ----
diff --git a/Documentation/core-api/asm-annotations.rst b/Documentation/core-api/asm-annotations.rst
index bc514ed598870c..d3071f131dad73 100644
--- a/Documentation/core-api/asm-annotations.rst
+++ b/Documentation/core-api/asm-annotations.rst
@@ -43,11 +43,10 @@ annotated objects like this, tools can be run on them to generate more useful
information. In particular, on properly annotated objects, ``objtool`` can be
run to check and fix the object if needed. Currently, ``objtool`` can report
missing frame pointer setup/destruction in functions. It can also
-automatically generate annotations for the ORC unwinder
-(Documentation/x86/orc-unwinder.rst)
+automatically generate annotations for the :ref:`ORC unwinder <orc-unwinder>`
for most code. Both of these are especially important to support reliable
-stack traces which are in turn necessary for kernel live patching
-(Documentation/livepatch/livepatch.rst).
+stack traces which are in turn necessary for :ref:`kernel live patching
+<kernel-livepatch>`.
Caveat and Discussion
---------------------
diff --git a/Documentation/livepatch/livepatch.rst b/Documentation/livepatch/livepatch.rst
index 68e3651e8af925..ebb8b05a9b0d3e 100644
--- a/Documentation/livepatch/livepatch.rst
+++ b/Documentation/livepatch/livepatch.rst
@@ -1,3 +1,5 @@
+.. _kernel-livepatch:
+
=========
Livepatch
=========
diff --git a/Documentation/x86/orc-unwinder.rst b/Documentation/x86/orc-unwinder.rst
index cdb257015bd9e8..b26368c3892d3d 100644
--- a/Documentation/x86/orc-unwinder.rst
+++ b/Documentation/x86/orc-unwinder.rst
@@ -1,5 +1,7 @@
.. SPDX-License-Identifier: GPL-2.0
+.. _orc-unwinder:
+
============
ORC unwinder
============
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-09-23 7:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:41 [PATCH v2 0/4] Rewrite the top-level index.rst Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 1/7] docs: promote the title of process/index.html Jonathan Corbet
2022-09-23 17:53 ` David Vernet
2022-09-23 18:31 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 2/7] docs: Rewrite the front page Jonathan Corbet
2022-09-23 19:02 ` Randy Dunlap
2022-09-23 19:07 ` Jonathan Corbet
2022-09-24 2:05 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 3/7] docs: reconfigure the HTML left column Jonathan Corbet
2022-09-24 2:13 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 4/7] docs: remove some index.rst cruft Jonathan Corbet
2022-09-24 2:14 ` David Vernet
2022-09-22 20:41 ` [PATCH v2 5/7] docs: move asm-annotations.rst into core-api Jonathan Corbet
2022-09-23 7:45 ` Bagas Sanjaya [this message]
2022-09-24 2:10 ` kernel test robot
2022-09-24 2:20 ` David Vernet
2022-09-25 3:54 ` Bagas Sanjaya
2022-09-25 21:29 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 6/7] docs: Expand the front-page CPU-architecture section Jonathan Corbet
2022-09-24 2:25 ` David Vernet
2022-09-25 21:50 ` Jonathan Corbet
2022-09-22 20:41 ` [PATCH v2 7/7] docs: put atomic*.txt and memory-barriers.txt into the core-api book Jonathan Corbet
2022-09-23 4:25 ` Bagas Sanjaya
2022-09-23 13:39 ` Jonathan Corbet
2022-09-25 3:18 ` Bagas Sanjaya
2022-09-25 3:48 ` Randy Dunlap
2022-09-25 3:52 ` Bagas Sanjaya
2022-09-23 18:44 ` Randy Dunlap
2022-09-23 19:06 ` Jonathan Corbet
2022-09-23 8:09 ` [PATCH v2 0/4] Rewrite the top-level index.rst Jani Nikula
2022-09-23 8:55 ` Thorsten Leemhuis
2022-09-23 13:45 ` Jonathan Corbet
2022-09-23 14:43 ` Thorsten Leemhuis
2022-09-23 15:03 ` Jonathan Corbet
2022-09-23 17:45 ` Kees Cook
2022-09-24 1:56 ` David Vernet
2022-09-23 18:48 ` Randy Dunlap
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=Yy1kHrS7ieq1VCqw@debian.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=jani.nikula@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
/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