From: Vincent Donnefort <vdonnefort@google.com>
To: maz@kernel.org, oupton@kernel.org, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org
Cc: joey.gouly@arm.com, seiden@linux.ibm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org,
kernel-team@android.com, fuad.tabba@linux.dev
Subject: Re: [PATCH] KVM: arm64: pkvm: Drop keneldoc markers for the allocator structs
Date: Mon, 5 Oct 2026 08:24:56 +0100 [thread overview]
Message-ID: <asNQyNI6nPcNuxwm@google.com> (raw)
In-Reply-To: <20261005072046.2246900-1-vdonnefort@google.com>
On Mon, Oct 05, 2026 at 08:20:46AM +0100, Vincent Donnefort wrote:
> chunk_hdr and hyp_allocator are private. Their description is not
> exposed to the API documentation. Drop the kerneldoc markers.
>
> While at it add the missing description for chunk_hdr::data.
>
> Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
I forgot the relevant tags
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202610041002.Yvw5qUrt-lkp@intel.com/
>
> diff --git a/arch/arm64/kvm/hyp/nvhe/alloc.c b/arch/arm64/kvm/hyp/nvhe/alloc.c
> index c1881c0011c9..e1e6dd21cda1 100644
> --- a/arch/arm64/kvm/hyp/nvhe/alloc.c
> +++ b/arch/arm64/kvm/hyp/nvhe/alloc.c
> @@ -28,13 +28,14 @@
> */
> #define MIN_ALLOC_SIZE 16UL
>
> -/**
> +/*
> * struct chunk_hdr - Chunk header
> * @next: offset from this chunk header to the next one.
> * @prev: offset from this chunk header to the previous one.
> * @__unmapped: Internal field containing the offset to the unmapped page
> * boundary, multiplexed with the allocation state flag.
> * @hash: Hash computed over the chunk header.
> + * @data: Chunk payload.
> */
> struct chunk_hdr {
> u32 next;
> @@ -45,7 +46,7 @@ struct chunk_hdr {
> char data[];
> } __aligned(MIN_ALLOC_SIZE);
>
> -/**
> +/*
> * struct hyp_allocator - Heap allocator
> * @start: Start in the allocator's reserved virtual address range.
> * @end: End in the allocator's reserved virtual address range.
>
> base-commit: f0406245cb9855e6318335a8a223551354291a46
> --
> 2.56.0.rc1.315.gc6ed9934b7-goog
>
--
Vincent
next prev parent reply other threads:[~2026-10-05 7:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 7:20 [PATCH] KVM: arm64: pkvm: Drop keneldoc markers for the allocator structs Vincent Donnefort
2026-10-05 7:24 ` Vincent Donnefort [this message]
2026-10-05 8:09 ` Marc Zyngier
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=asNQyNI6nPcNuxwm@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).