From: kernel test robot <[email protected]>
To: Ammar Faizi <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>
Subject: [ammarfaizi2-block:testing/af/home] BUILD SUCCESS WITH WARNING 51fb2efd62ae52dc061dbca301fb823357fb3f80
Date: Wed, 31 May 2023 17:39:16 +0800 [thread overview]
Message-ID: <20230531093916.3Tm8t%[email protected]> (raw)
tree/branch: https://github.com/ammarfaizi2/linux-block testing/af/home
branch HEAD: 51fb2efd62ae52dc061dbca301fb823357fb3f80 btrfs: Add `BTRFS_DEFAULT_MAX_THREAD_POOL_SIZE` macro
Warning reports:
https://lore.kernel.org/oe-kbuild-all/[email protected]
Warning: (recently discovered and may have been fixed)
kernel/workqueue.c:4421:5: warning: no previous prototype for 'set_workqueue_cpumask' [-Wmissing-prototypes]
Warning ids grouped by kconfigs:
gcc_recent_errors
|-- alpha-allyesconfig
| `-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
|-- csky-defconfig
| `-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
|-- m68k-allyesconfig
| `-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
|-- mips-allyesconfig
| `-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
|-- parisc-allyesconfig
| `-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
`-- powerpc-allyesconfig
`-- kernel-workqueue.c:warning:no-previous-prototype-for-set_workqueue_cpumask
elapsed time: 725m
configs tested: 42
configs skipped: 5
tested configs:
alpha allyesconfig gcc
alpha defconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm64 allyesconfig gcc
arm64 defconfig gcc
csky defconfig gcc
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
loongarch randconfig-r002-20230531 gcc
m68k allmodconfig gcc
m68k defconfig gcc
mips allmodconfig gcc
mips allyesconfig gcc
mips randconfig-r001-20230531 clang
nios2 defconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv defconfig gcc
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
sh allmodconfig gcc
sparc defconfig gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 rhel-8.3 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-05-31 9:40 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=20230531093916.3Tm8t%[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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