From: Mike Rapoport <rppt@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Alexander Graf <graf@amazon.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, usamaarif642@gmail.com, rmikey@meta.com,
clm@fb.com, riel@surriel.com, SeongJae Park <sj@kernel.org>,
kernel-team@meta.com
Subject: Re: [PATCH v6 2/4] kho: rename fdt parameter to blob in kho_add/remove_subtree()
Date: Tue, 27 Jan 2026 16:43:06 +0200 [thread overview]
Message-ID: <aXjO-jQ2_pzVcp9o@kernel.org> (raw)
In-Reply-To: <20260127-kho-v6-2-56f9396681c2@debian.org>
On Tue, Jan 27, 2026 at 06:37:37AM -0800, Breno Leitao wrote:
> Since kho_add_subtree() now accepts arbitrary data blobs (not just
> FDTs), rename the parameter from 'fdt' to 'blob' to better reflect
> its purpose. Apply the same rename to kho_remove_subtree() for
> consistency.
>
> Also rename kho_debugfs_fdt_add() and kho_debugfs_fdt_remove() to
> kho_debugfs_blob_add() and kho_debugfs_blob_remove() respectively,
> with the same parameter rename from 'fdt' to 'blob'.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-01-27 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 14:37 [PATCH v6 0/4] kho: history: track previous kernel version and kexec boot count Breno Leitao
2026-01-27 14:37 ` [PATCH v6 1/4] kho: add size parameter to kho_add_subtree() Breno Leitao
2026-02-04 13:54 ` Pratyush Yadav
2026-03-06 11:47 ` Breno Leitao
2026-01-27 14:37 ` [PATCH v6 2/4] kho: rename fdt parameter to blob in kho_add/remove_subtree() Breno Leitao
2026-01-27 14:43 ` Mike Rapoport [this message]
2026-01-27 14:37 ` [PATCH v6 3/4] kho: kexec-metadata: track previous kernel chain Breno Leitao
2026-01-27 14:37 ` [PATCH v6 4/4] kho: document kexec-metadata tracking feature Breno Leitao
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=aXjO-jQ2_pzVcp9o@kernel.org \
--to=rppt@kernel.org \
--cc=clm@fb.com \
--cc=graf@amazon.com \
--cc=kernel-team@meta.com \
--cc=kexec@lists.infradead.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=riel@surriel.com \
--cc=rmikey@meta.com \
--cc=sj@kernel.org \
--cc=usamaarif642@gmail.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 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.