From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [paulmck-rcu:non-rcu:next] BUILD SUCCESS WITH UNVERIFIED WARNING 9d7a5ab4d4dfb32cd8638d544a5bc47f51f3a9f7
Date: Fri, 11 Sep 2026 02:10:58 +0800 [thread overview]
Message-ID: <202609110250.IFsYXPrU-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git non-rcu/next
branch HEAD: 9d7a5ab4d4dfb32cd8638d544a5bc47f51f3a9f7 Merge branches 'csd-lock.2026.09.03a', 'hazptr.2026.09.03a' and 'hrtimer_sleeper.2026.09.03a' into HEAD
Unverified Warning (likely false positive, kindly check if interested):
https://lore.kernel.org/oe-kbuild/202609110217.JyIWm88m-lkp@intel.com
drivers/hid/hid-steam.c:557 steam_send_report_id() warn: check sign expansion for '__UNIQUE_ID_x__463'
Warning ids grouped by kconfigs:
recent_errors
`-- x86_64-randconfig-161-20260910
`-- drivers-hid-hid-steam.c-steam_send_report_id()-warn:check-sign-expansion-for-__UNIQUE_ID_x__463
elapsed time: 1468m
configs tested: 71
configs skipped: 0
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
arc allmodconfig clang-24
arc allmodconfig gcc-16.1.0
arc allnoconfig gcc-16.1.0
arc allyesconfig clang-24
arm allnoconfig clang-17
arm allyesconfig clang-24
arm64 allmodconfig clang-24
arm64 allnoconfig gcc-16.1.0
csky allmodconfig gcc-16.1.0
csky allnoconfig gcc-16.1.0
hexagon allmodconfig gcc-16.1.0
hexagon allnoconfig clang-24
i386 allmodconfig clang-22
i386 allnoconfig gcc-14
i386 allyesconfig clang-22
loongarch allmodconfig clang-24
loongarch allnoconfig clang-20
m68k allmodconfig gcc-16.1.0
m68k allnoconfig gcc-16.1.0
m68k allyesconfig clang-24
m68k allyesconfig gcc-16.1.0
microblaze allnoconfig gcc-16.1.0
microblaze allyesconfig gcc-16.1.0
mips allmodconfig gcc-16.1.0
mips allnoconfig gcc-16.1.0
mips allyesconfig gcc-16.1.0
nios2 allmodconfig clang-20
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig clang-24
nios2 allnoconfig gcc-11.5.0
openrisc allmodconfig clang-20
openrisc allmodconfig gcc-16.1.0
openrisc allnoconfig clang-24
openrisc allnoconfig gcc-16.1.0
parisc allmodconfig gcc-16.1.0
parisc allnoconfig clang-24
parisc allnoconfig gcc-16.1.0
parisc allyesconfig clang-17
powerpc allmodconfig gcc-16.1.0
powerpc allnoconfig clang-24
powerpc allnoconfig gcc-16.1.0
riscv allmodconfig clang-24
riscv allnoconfig clang-24
riscv allnoconfig gcc-16.1.0
riscv allyesconfig clang-24
s390 allmodconfig clang-17
s390 allnoconfig clang-24
s390 allyesconfig gcc-16.1.0
sh allmodconfig gcc-16.1.0
sh allnoconfig clang-24
sh allnoconfig gcc-16.1.0
sh allyesconfig clang-17
sh allyesconfig gcc-16.1.0
sparc allnoconfig clang-24
sparc allnoconfig gcc-16.1.0
sparc64 allmodconfig clang-20
um allmodconfig clang-17
um allnoconfig clang-17
um allnoconfig clang-24
um allyesconfig gcc-16.1.0
x86_64 allmodconfig clang-22
x86_64 allnoconfig clang-22
x86_64 allnoconfig clang-24
x86_64 allyesconfig clang-22
x86_64 rhel-9.4-rust clang-22
xtensa allnoconfig clang-24
xtensa allnoconfig gcc-16.1.0
xtensa allyesconfig clang-20
xtensa allyesconfig gcc-16.1.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-10 18:11 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=202609110250.IFsYXPrU-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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
all inboxes | Powered by JetHome®