From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [gustavoars:testing/wfamnae-next20250616 19/19] include/asm-generic/tlb.h:378:2: error: type name requires a specifier or qualifier
Date: Thu, 26 Jun 2025 08:07:03 +0800 [thread overview]
Message-ID: <202506260845.3py4BoAJ-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux.git testing/wfamnae-next20250616
head: 78f053980ba50a0becae798ab7d07527d97e790d
commit: 78f053980ba50a0becae798ab7d07527d97e790d [19/19] treewide: Avoid -Wflex-array-member-not-at-end warnings
config: s390-allnoconfig (https://download.01.org/0day-ci/archive/20250626/202506260845.3py4BoAJ-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project e04c938cc08a90ae60440ce22d072ebc69d67ee8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250626/202506260845.3py4BoAJ-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/202506260845.3py4BoAJ-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from mm/oom_kill.c:49:
In file included from arch/s390/include/asm/tlb.h:38:
>> include/asm-generic/tlb.h:378:2: error: type name requires a specifier or qualifier
378 | );};
| ^
>> include/asm-generic/tlb.h:378:2: error: expected member name or ';' after declaration specifiers
>> include/asm-generic/tlb.h:367:28: error: expected ';' at end of declaration list
367 | unsigned int batch_count;
| ^
| ;
3 errors generated.
vim +378 include/asm-generic/tlb.h
327
328 unsigned long start;
329 unsigned long end;
330 /*
331 * we are in the middle of an operation to clear
332 * a full mm and can make some optimizations
333 */
334 unsigned int fullmm : 1;
335
336 /*
337 * we have performed an operation which
338 * requires a complete flush of the tlb
339 */
340 unsigned int need_flush_all : 1;
341
342 /*
343 * we have removed page directories
344 */
345 unsigned int freed_tables : 1;
346
347 /*
348 * Do we have pending delayed rmap removals?
349 */
350 unsigned int delayed_rmap : 1;
351
352 /*
353 * at which levels have we cleared entries?
354 */
355 unsigned int cleared_ptes : 1;
356 unsigned int cleared_pmds : 1;
357 unsigned int cleared_puds : 1;
358 unsigned int cleared_p4ds : 1;
359
360 /*
361 * tracks VM_EXEC | VM_HUGETLB in tlb_start_vma
362 */
363 unsigned int vma_exec : 1;
364 unsigned int vma_huge : 1;
365 unsigned int vma_pfn : 1;
366
> 367 unsigned int batch_count;
368
369 #ifndef CONFIG_MMU_GATHER_NO_GATHER
370 struct mmu_gather_batch *active;
371 TRAILING_OVERLAP(struct mmu_gather_batch, local, encoded_pages,
372 struct page *__pages[MMU_GATHER_BUNDLE];
373
374 #ifdef CONFIG_MMU_GATHER_PAGE_SIZE
375 unsigned int page_size;
376 #endif
377 #endif
> 378 );};
379
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-26 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202506260845.3py4BoAJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.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
all inboxes | Powered by JetHome®