From: Pratyush Yadav <pratyush@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>,
Jason Miu <jasonmiu@google.com>,
Jonathan Corbet <corbet@lwn.net>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/6] kho: docs: combine concepts and FDT documentation
Date: Tue, 20 Jan 2026 18:36:33 +0000 [thread overview]
Message-ID: <2vxzikcwcery.fsf@kernel.org> (raw)
In-Reply-To: <aW_K7QZj8HYzA00t@kernel.org> (Mike Rapoport's message of "Tue, 20 Jan 2026 20:35:25 +0200")
On Tue, Jan 20 2026, Mike Rapoport wrote:
> On Tue, Jan 20, 2026 at 04:08:56PM +0000, Pratyush Yadav wrote:
>> On Mon, Jan 05 2026, Mike Rapoport wrote:
>>
>> > From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>> >
>> > Currently index.rst in KHO documentation looks empty and sad as it only
>> > contains links to "Kexec Handover Concepts" and "KHO FDT" chapters.
>> >
>> > Inline contents of these chapters into index.rst to provide a single
>> > coherent chapter describing KHO.
>> >
>> > While on it, drop parts of the KHO FDT description that will be superseded
>> > by addition of KHO ABI documentation.
>> >
>> > Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>> [...]
>> > diff --git a/Documentation/core-api/kho/index.rst b/Documentation/core-api/kho/index.rst
>> > index 0c63b0c5c143..03cd9afbdb2e 100644
>> > --- a/Documentation/core-api/kho/index.rst
>> > +++ b/Documentation/core-api/kho/index.rst
>> > @@ -4,10 +4,73 @@
>> > Kexec Handover Subsystem
>> > ========================
>> >
>> > -.. toctree::
>> > - :maxdepth: 1
>> > +Overview
>> > +========
>>
>> I ran a test build and Sphinx complains about:
>>
>> Documentation/admin-guide/mm/kho.rst:10: WARNING: undefined label: 'kho-concepts' [ref.ref]
>> Documentation/admin-guide/mm/kho.rst:31: WARNING: undefined label: 'kho-finalization-phase' [ref.ref]
>>
>> I suppose you should add these labels here.
>
> It's already in Andrew's tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/commit/?h=mm-nonmm-unstable&id=bc1a060da2a76161ba65f1badc551de15056e398
Okay, nice. Then with that,
Reviewed-by: Pratyush Yadav <pratyush@kernel.org>
>
>> Otherwise LGTM.
>>
[...]
--
Regards,
Pratyush Yadav
next prev parent reply other threads:[~2026-01-20 18:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:58 [PATCH 0/6] kho: ABI headers and Documentation updates Mike Rapoport
2026-01-05 16:58 ` [PATCH 1/6] kho/abi: luo: make generated documentation more coherent Mike Rapoport
2026-01-20 15:48 ` Pratyush Yadav
2026-01-22 18:27 ` Pasha Tatashin
2026-01-05 16:58 ` [PATCH 2/6] kho/abi: memfd: " Mike Rapoport
2026-01-20 15:49 ` Pratyush Yadav
2026-01-22 18:28 ` Pasha Tatashin
2026-01-05 16:58 ` [PATCH 3/6] kho: docs: combine concepts and FDT documentation Mike Rapoport
2026-01-20 16:08 ` Pratyush Yadav
2026-01-20 18:35 ` Mike Rapoport
2026-01-20 18:36 ` Pratyush Yadav [this message]
2026-01-22 18:27 ` Pasha Tatashin
2026-01-05 16:58 ` [PATCH 4/6] kho: Introduce KHO FDT ABI header Mike Rapoport
2026-01-20 16:14 ` Pratyush Yadav
2026-01-22 18:29 ` Pasha Tatashin
2026-01-05 16:58 ` [PATCH 5/6] kho: Relocate vmalloc preservation structure to KHO " Mike Rapoport
2026-01-20 16:26 ` Pratyush Yadav
2026-01-20 18:42 ` Mike Rapoport
2026-01-20 18:56 ` Pratyush Yadav
2026-01-22 18:24 ` Pasha Tatashin
2026-01-05 16:58 ` [PATCH 6/6] kho/abi: add memblock " Mike Rapoport
2026-01-20 16:31 ` Pratyush Yadav
2026-01-20 18:44 ` Mike Rapoport
2026-01-22 18:25 ` Pasha Tatashin
2026-01-20 16:32 ` [PATCH 0/6] kho: ABI headers and Documentation updates Pratyush Yadav
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=2vxzikcwcery.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=rppt@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.