From: Mike Rapoport <rppt@kernel.org>
To: Pasha Tatashin <pasha.tatashin@soleen.com>
Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org,
akpm@linux-foundation.org, linux-mm@kvack.org,
skhan@linuxfoundation.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, corbet@lwn.net,
dmatlack@google.com, kexec@lists.infradead.org,
pratyush@kernel.org, skhawaja@google.com, graf@amazon.com
Subject: Re: [PATCH v6 04/13] liveupdate: register luo_ser as KHO subtree
Date: Wed, 3 Jun 2026 12:32:54 +0300 [thread overview]
Message-ID: <ah_0xsPC_oNPewVk@kernel.org> (raw)
In-Reply-To: <178046942429.468621.9591914636403075487.b4-review@b4>
On Wed, Jun 03, 2026 at 09:50:24AM +0300, Mike Rapoport wrote:
> # Add your code comments below. There is no need to trim or delete
> # any existing content -- just insert your comments under the relevant
> # lines of code. Lines starting with "> " are quoted diff context and
> # lines starting with "| " are comments from other reviewers.
> # The final email will be reformatted automatically to include only
> # the sections that have your comments.
> #
looks like b4 review bug or misuse from my side :)
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-06-03 9:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 3:28 [PATCH v6 00/13] liveupdate: Remove limits on sessions and files Pasha Tatashin
2026-06-03 3:28 ` [PATCH v6 01/13] liveupdate: change file_set->count type to u64 for type safety Pasha Tatashin
2026-06-03 3:28 ` [PATCH v6 02/13] liveupdate: avoid mixing cleanup guards with goto in luo_session_retrieve_fd Pasha Tatashin
2026-06-03 6:52 ` Mike Rapoport
2026-06-03 3:28 ` [PATCH v6 03/13] liveupdate: centralize state management into struct luo_ser Pasha Tatashin
2026-06-03 6:52 ` Mike Rapoport
2026-06-03 3:28 ` [PATCH v6 04/13] liveupdate: register luo_ser as KHO subtree Pasha Tatashin
2026-06-03 6:50 ` Mike Rapoport
2026-06-03 9:32 ` Mike Rapoport [this message]
2026-06-03 3:28 ` [PATCH v6 05/13] liveupdate: Extract luo_file_deserialize_one helper Pasha Tatashin
2026-06-03 3:28 ` [PATCH v6 06/13] liveupdate: Extract luo_session_deserialize_one helper Pasha Tatashin
2026-06-03 3:28 ` [PATCH v6 07/13] kho: add support for linked-block serialization Pasha Tatashin
2026-06-03 6:49 ` Mike Rapoport
2026-06-03 12:05 ` Pasha Tatashin
2026-06-03 3:28 ` [PATCH v6 08/13] liveupdate: defer session block allocation and physical address setting Pasha Tatashin
2026-06-03 3:29 ` [PATCH v6 09/13] liveupdate: Remove limit on the number of sessions Pasha Tatashin
2026-06-03 3:29 ` [PATCH v6 10/13] liveupdate: Remove limit on the number of files per session Pasha Tatashin
2026-06-03 3:29 ` [PATCH v6 11/13] selftests/liveupdate: Test session and file limit removal Pasha Tatashin
2026-06-03 3:29 ` [PATCH v6 12/13] selftests/liveupdate: Add stress-sessions kexec test Pasha Tatashin
2026-06-03 3:29 ` [PATCH v6 13/13] selftests/liveupdate: Add stress-files " Pasha Tatashin
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=ah_0xsPC_oNPewVk@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=skhawaja@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