From: kernel test robot <lkp@intel.com>
To: Jason Miu <jasonmiu@google.com>, Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Changyuan Lyu <changyuanl@google.com>,
David Matlack <dmatlack@google.com>,
David Rientjes <rientjes@google.com>,
Jason Gunthorpe <jgg@nvidia.com>, Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH v8 1/2] kho: Adopt radix tree for preserved memory tracking
Date: Fri, 30 Jan 2026 11:28:47 +0100 [thread overview]
Message-ID: <202601301107.1CQsWeRT-lkp@intel.com> (raw)
In-Reply-To: <20260130005739.3163049-2-jasonmiu@google.com>
Hi Jason,
kernel test robot noticed the following build errors:
[auto build test ERROR on 33a647c659ffa5bdb94abc345c8c86768ff96215]
url: https://github.com/intel-lab-lkp/linux/commits/Jason-Miu/kho-Adopt-radix-tree-for-preserved-memory-tracking/20260130-090027
base: 33a647c659ffa5bdb94abc345c8c86768ff96215
patch link: https://lore.kernel.org/r/20260130005739.3163049-2-jasonmiu%40google.com
patch subject: [PATCH v8 1/2] kho: Adopt radix tree for preserved memory tracking
reproduce: (https://download.01.org/0day-ci/archive/20260130/202601301107.1CQsWeRT-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/202601301107.1CQsWeRT-lkp@intel.com/
All errors (new ones prefixed by >>):
WARNING: No kernel-doc for file ./include/linux/kho/abi/kexec_handover.h
ERROR: Cannot find file ./include/linux/kho/abi/memblock.h
WARNING: No kernel-doc for file ./include/linux/kho/abi/memblock.h
ERROR: Cannot find file ./include/linux/kho/abi/kexec_handover.h
WARNING: No kernel-doc for file ./include/linux/kho/abi/kexec_handover.h
>> ERROR: Cannot find file ./include/linux/kho_radix_tree.h
WARNING: No kernel-doc for file ./include/linux/kho_radix_tree.h
ERROR: Cannot find file ./include/linux/kref.h
WARNING: No kernel-doc for file ./include/linux/kref.h
ERROR: Cannot find file ./include/linux/rslib.h
ERROR: Cannot find file ./include/linux/rslib.h
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-30 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 0:57 [PATCH v8 0/2] Make KHO Stateless Jason Miu
2026-01-30 0:57 ` [PATCH v8 1/2] kho: Adopt radix tree for preserved memory tracking Jason Miu
2026-01-30 10:28 ` kernel test robot [this message]
2026-02-03 16:16 ` Mike Rapoport
2026-02-06 2:17 ` Jason Miu
2026-01-30 0:57 ` [PATCH v8 2/2] kho: Remove finalize state and clients Jason Miu
2026-02-03 16:18 ` Mike Rapoport
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=202601301107.1CQsWeRT-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=changyuanl@google.com \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=jasonmiu@google.com \
--cc=jgg@nvidia.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=rientjes@google.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