From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org
Subject: [groeck-staging:hwmon-next] BUILD SUCCESS 04dc3c9e432a63a87424b9c974c2e95d449ac5f0
Date: Thu, 13 Apr 2023 12:57:07 +0800 [thread overview]
Message-ID: <64378ba3.3VYLiyjP7lc1mMU1%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
branch HEAD: 04dc3c9e432a63a87424b9c974c2e95d449ac5f0 hwmon: (nct6775) update ASUS WMI monitoring list A620/B760/W790
elapsed time: 728m
configs tested: 85
configs skipped: 8
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
alpha buildonly-randconfig-r006-20230410 gcc
alpha defconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-r043-20230412 gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm buildonly-randconfig-r002-20230409 clang
arm buildonly-randconfig-r005-20230409 clang
arm defconfig gcc
arm randconfig-r046-20230412 clang
arm64 allyesconfig gcc
arm64 defconfig gcc
csky defconfig gcc
hexagon randconfig-r041-20230412 clang
hexagon randconfig-r045-20230412 clang
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-a001-20230410 clang
i386 randconfig-a002-20230410 clang
i386 randconfig-a003-20230410 clang
i386 randconfig-a004-20230410 clang
i386 randconfig-a005-20230410 clang
i386 randconfig-a006-20230410 clang
i386 randconfig-a011-20230410 gcc
i386 randconfig-a012-20230410 gcc
i386 randconfig-a013-20230410 gcc
i386 randconfig-a014-20230410 gcc
i386 randconfig-a015-20230410 gcc
i386 randconfig-a016-20230410 gcc
ia64 allmodconfig gcc
ia64 buildonly-randconfig-r006-20230409 gcc
ia64 defconfig gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch buildonly-randconfig-r005-20230410 gcc
loongarch defconfig gcc
m68k allmodconfig gcc
m68k defconfig gcc
m68k randconfig-r021-20230410 gcc
m68k randconfig-r024-20230409 gcc
microblaze buildonly-randconfig-r002-20230410 gcc
microblaze randconfig-r023-20230410 gcc
mips allmodconfig gcc
mips allyesconfig gcc
nios2 buildonly-randconfig-r004-20230409 gcc
nios2 defconfig gcc
openrisc randconfig-r024-20230410 gcc
parisc buildonly-randconfig-r001-20230410 gcc
parisc buildonly-randconfig-r003-20230410 gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc randconfig-r026-20230410 gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv buildonly-randconfig-r004-20230410 gcc
riscv defconfig gcc
riscv randconfig-r042-20230412 gcc
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-r044-20230412 gcc
sh allmodconfig gcc
sparc buildonly-randconfig-r001-20230409 gcc
sparc defconfig gcc
sparc64 randconfig-r022-20230410 gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a001-20230410 clang
x86_64 randconfig-a002-20230410 clang
x86_64 randconfig-a003-20230410 clang
x86_64 randconfig-a004-20230410 clang
x86_64 randconfig-a005-20230410 clang
x86_64 randconfig-a006-20230410 clang
x86_64 rhel-8.3 gcc
xtensa buildonly-randconfig-r003-20230409 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-04-13 4:57 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=64378ba3.3VYLiyjP7lc1mMU1%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).