From: kernel test robot <lkp@intel.com>
To: Ronan Marchal <ronanmarchal29@gmail.com>, rafael@kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
pavel@kernel.org, lenb@kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ronan Marchal <ronanmarchal29@gmail.com>
Subject: Re: [PATCH] kernel/power/snapshot: Add missing kernel-doc parameter descriptions
Date: Mon, 15 Jun 2026 04:31:12 +0800 [thread overview]
Message-ID: <202606150431.R9kR0q9p-lkp@intel.com> (raw)
In-Reply-To: <20260614144158.82751-1-ronanmarchal29@gmail.com>
Hi Ronan,
kernel test robot noticed the following build errors:
[auto build test ERROR on amd-pstate/linux-next]
[also build test ERROR on amd-pstate/bleeding-edge linus/master v7.1 next-20260612]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ronan-Marchal/kernel-power-snapshot-Add-missing-kernel-doc-parameter-descriptions/20260614-224612
base: https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git linux-next
patch link: https://lore.kernel.org/r/20260614144158.82751-1-ronanmarchal29%40gmail.com
patch subject: [PATCH] kernel/power/snapshot: Add missing kernel-doc parameter descriptions
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20260615/202606150431.R9kR0q9p-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260615/202606150431.R9kR0q9p-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/202606150431.R9kR0q9p-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/power/snapshot.c:2042:1: error: unknown type name 'c'
2042 | c/**
| ^
1 error generated.
vim +/c +2042 kernel/power/snapshot.c
2041
> 2042 c/**
2043 * enough_free_mem - Check if there is enough free memory for the image.
2044 * @nr_pages: Number of non-highmem pages to copy.
2045 * @nr_highmem: Number of highmem pages to copy.
2046 *
2047 * Check if there are enough free non-highmem pages available to save
2048 * the hibernation image.
2049 */
2050 static int enough_free_mem(unsigned int nr_pages, unsigned int nr_highmem)
2051 {
2052 struct zone *zone;
2053 unsigned int free = alloc_normal;
2054
2055 for_each_populated_zone(zone)
2056 if (!is_highmem(zone))
2057 free += zone_page_state(zone, NR_FREE_PAGES);
2058
2059 nr_pages += count_pages_for_highmem(nr_highmem);
2060 pr_debug("Normal pages needed: %u + %u, available pages: %u\n",
2061 nr_pages, PAGES_FOR_IO, free);
2062
2063 return free > nr_pages + PAGES_FOR_IO;
2064 }
2065
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2026-06-14 20:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260614144158.82751-1-ronanmarchal29@gmail.com>]
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=202606150431.R9kR0q9p-lkp@intel.com \
--to=lkp@intel.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@kernel.org \
--cc=rafael@kernel.org \
--cc=ronanmarchal29@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox