From: kernel test robot <lkp@intel.com>
To: Vitaly Wool <vitaly.wool@konsulko.se>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
akpm@linux-foundation.org, hannes@cmpxchg.org,
minchan@kernel.org, nphamcs@gmail.com, senozhatsky@chromium.org,
shakeel.butt@linux.dev, yosry.ahmed@linux.dev,
Igor Belousov <igor.b@beldev.am>,
Vitaly Wool <vitaly.wool@konsulko.se>
Subject: Re: [PATCH mm-new] mm/zblock: add debugfs
Date: Mon, 28 Apr 2025 09:32:53 +0800 [thread overview]
Message-ID: <202504280934.X1Gqvqj1-lkp@intel.com> (raw)
In-Reply-To: <20250427201958.491806-1-vitaly.wool@konsulko.se>
Hi Vitaly,
kernel test robot noticed the following build errors:
[auto build test ERROR on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Vitaly-Wool/mm-zblock-add-debugfs/20250428-042209
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20250427201958.491806-1-vitaly.wool%40konsulko.se
patch subject: [PATCH mm-new] mm/zblock: add debugfs
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250428/202504280934.X1Gqvqj1-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250428/202504280934.X1Gqvqj1-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/202504280934.X1Gqvqj1-lkp@intel.com/
All errors (new ones prefixed by >>):
>> mm/zblock.c:125:46: error: no member named 'num_pages' in 'struct block_desc'
125 | i, block_list->block_count, block_desc[i].num_pages,
| ~~~~~~~~~~~~~ ^
mm/zblock.c:126:44: error: no member named 'num_pages' in 'struct block_desc'
126 | block_list->block_count * block_desc[i].num_pages);
| ~~~~~~~~~~~~~ ^
2 errors generated.
vim +125 mm/zblock.c
115
116 static int zblock_blocks_show(struct seq_file *s, void *v)
117 {
118 struct zblock_pool *pool = s->private;
119 int i;
120
121 for (i = 0; i < ARRAY_SIZE(block_desc); i++) {
122 struct block_list *block_list = &pool->block_lists[i];
123
124 seq_printf(s, "%d: %ld blocks of %d pages (total %ld pages)\n",
> 125 i, block_list->block_count, block_desc[i].num_pages,
126 block_list->block_count * block_desc[i].num_pages);
127 }
128 return 0;
129 }
130 DEFINE_SHOW_ATTRIBUTE(zblock_blocks);
131
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-04-28 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-27 20:19 Vitaly Wool
2025-04-28 1:32 ` kernel test robot [this message]
2025-04-28 4:48 ` kernel test robot
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=202504280934.X1Gqvqj1-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=igor.b@beldev.am \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=llvm@lists.linux.dev \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=senozhatsky@chromium.org \
--cc=shakeel.butt@linux.dev \
--cc=vitaly.wool@konsulko.se \
--cc=yosry.ahmed@linux.dev \
/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