From: kernel test robot <lkp@intel.com>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: oe-kbuild-all@lists.linux.dev, Marc Zyngier <maz@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>
Subject: [linux-next:master 13847/14185] Warning: arch/arm64/kvm/hyp/nvhe/alloc.c:45 struct member 'data' not described in 'chunk_hdr'
Date: Sun, 04 Oct 2026 10:53:02 +0800 [thread overview]
Message-ID: <202610041002.Yvw5qUrt-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: f0406245cb9855e6318335a8a223551354291a46
commit: c8d7834c9c219a9a0e3969986e90c5c444b9d98d [13847/14185] KVM: arm64: Add a heap allocator for the pKVM hyp
config: arm64-defconfig (https://download.01.org/0day-ci/archive/20261004/202610041002.Yvw5qUrt-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 16.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261004/202610041002.Yvw5qUrt-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610041002.Yvw5qUrt-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Warning: arch/arm64/kvm/hyp/nvhe/alloc.c:45 struct member 'data' not described in 'chunk_hdr'
>> Warning: arch/arm64/kvm/hyp/nvhe/alloc.c:45 struct member 'data' not described in 'chunk_hdr'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-10-04 2:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 2:53 kernel test robot [this message]
2026-10-04 9:40 ` [linux-next:master 13847/14185] Warning: arch/arm64/kvm/hyp/nvhe/alloc.c:45 struct member 'data' not described in 'chunk_hdr' 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=202610041002.Yvw5qUrt-lkp@intel.com \
--to=lkp@intel.com \
--cc=fuad.tabba@linux.dev \
--cc=maz@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vdonnefort@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 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.