From: Pratyush Yadav <pratyush@kernel.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: 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>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/6] kho: ABI headers and Documentation updates
Date: Tue, 20 Jan 2026 16:32:32 +0000 [thread overview]
Message-ID: <2vxzms28ckin.fsf@kernel.org> (raw)
In-Reply-To: <20260105165839.285270-1-rppt@kernel.org> (Mike Rapoport's message of "Mon, 5 Jan 2026 18:58:33 +0200")
On Mon, Jan 05 2026, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> Hi,
>
> LUO started adding KHO ABI headers to include/linux/kho/abi, but the
> core parts of KHO and memblock are still using the old way for
> descriptions on their ABIs.
>
> Let's consolidate all things KHO in include/linux/kho/abi.
>
> And while on that, make some documentation updates to have more coherent
> KHO docs.
Thanks for working on this! It is nice to have the ABI consolidated and
cleaned.
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-01-20 16:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:58 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
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 ` Pratyush Yadav [this message]
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=2vxzms28ckin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox