From: kernel test robot <lkp@intel.com>
To: hamjin <jinham@qq.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, hamjin <jinham@qq.com>
Subject: Re: [PATCH] lib: typecheck: initialize const variable to avoid Clang warning
Date: Wed, 25 Mar 2026 20:52:21 +0800 [thread overview]
Message-ID: <202603252052.cM1GQIHa-lkp@intel.com> (raw)
In-Reply-To: <tencent_274FD06231C70768C2C28FD13673A24C2B08@qq.com>
Hi hamjin,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v7.0-rc5 next-20260324]
[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/hamjin/lib-typecheck-initialize-const-variable-to-avoid-Clang-warning/20260315-165617
base: linus/master
patch link: https://lore.kernel.org/r/tencent_274FD06231C70768C2C28FD13673A24C2B08%40qq.com
patch subject: [PATCH] lib: typecheck: initialize const variable to avoid Clang warning
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20260325/202603252052.cM1GQIHa-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260325/202603252052.cM1GQIHa-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/202603252052.cM1GQIHa-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from arch/s390/include/asm/lowcore.h:14,
from arch/s390/include/asm/current.h:13,
from include/linux/sched.h:12,
from arch/s390/kernel/asm-offsets.c:10:
arch/s390/include/asm/ptrace.h: In function 'user_mode':
>> arch/s390/include/asm/ptrace.h:224:9: error: conversion to non-scalar type requested
224 | return psw_bits(regs->psw).pstate;
| ^~~~~~
make[3]: *** [scripts/Makefile.build:184: arch/s390/kernel/asm-offsets.s] Error 1
make[3]: Target 'prepare' not remade because of errors.
make[2]: *** [Makefile:1337: prepare0] Error 2
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2
make: Target 'prepare' not remade because of errors.
vim +224 arch/s390/include/asm/ptrace.h
952974ac61f686 Heiko Carstens 2010-02-12 221
afa8fa52a42c31 Jens Remus 2025-12-11 222 static __always_inline bool user_mode(const struct pt_regs *regs)
afa8fa52a42c31 Jens Remus 2025-12-11 223 {
afa8fa52a42c31 Jens Remus 2025-12-11 @224 return psw_bits(regs->psw).pstate;
afa8fa52a42c31 Jens Remus 2025-12-11 225 }
afa8fa52a42c31 Jens Remus 2025-12-11 226
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-03-25 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 8:52 hamjin
2026-03-15 15:12 ` kernel test robot
2026-03-25 12:07 ` kernel test robot
2026-03-25 12:52 ` kernel test robot [this message]
2026-03-26 2:04 ` Nathan Chancellor
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=202603252052.cM1GQIHa-lkp@intel.com \
--to=lkp@intel.com \
--cc=jinham@qq.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome