From: kernel test robot <lkp@intel.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org
Subject: [hwmon:hwmon] BUILD SUCCESS 09aa62c08b99fdc55f9491e3170b0b6b3476fdaf
Date: Mon, 15 Jun 2020 13:48:20 +0800 [thread overview]
Message-ID: <5ee70ba4.HhGBcpaXT2jVn6Dh%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon
branch HEAD: 09aa62c08b99fdc55f9491e3170b0b6b3476fdaf hwmon: (bt1-pvt) Mark is_visible functions static
elapsed time: 484m
configs tested: 126
configs skipped: 5
The following configs have been built successfully.
More configs may be tested in the coming days.
arm defconfig
arm allyesconfig
arm allmodconfig
arm allnoconfig
arm64 allyesconfig
arm64 defconfig
arm64 allmodconfig
arm64 allnoconfig
sh rsk7269_defconfig
arc nsim_700_defconfig
powerpc holly_defconfig
sparc64 alldefconfig
arm multi_v4t_defconfig
powerpc cell_defconfig
sh se7750_defconfig
powerpc pq2fads_defconfig
arm versatile_defconfig
mips bcm47xx_defconfig
h8300 defconfig
arc haps_hs_smp_defconfig
mips ar7_defconfig
arm badge4_defconfig
mips loongson3_defconfig
sh se7206_defconfig
x86_64 defconfig
arm efm32_defconfig
powerpc64 defconfig
powerpc wii_defconfig
mips ath79_defconfig
sh cayman_defconfig
arm sama5_defconfig
arm stm32_defconfig
arm viper_defconfig
m68k multi_defconfig
h8300 h8s-sim_defconfig
xtensa generic_kc705_defconfig
m68k amiga_defconfig
arm tegra_defconfig
mips db1xxx_defconfig
mips cu1000-neo_defconfig
arm s5pv210_defconfig
powerpc mpc7448_hpc2_defconfig
i386 allnoconfig
i386 allyesconfig
i386 defconfig
i386 debian-10.3
ia64 allmodconfig
ia64 defconfig
ia64 allnoconfig
ia64 allyesconfig
m68k allmodconfig
m68k allnoconfig
m68k sun3_defconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
nios2 allyesconfig
openrisc defconfig
c6x allyesconfig
c6x allnoconfig
openrisc allyesconfig
nds32 defconfig
nds32 allnoconfig
csky allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
h8300 allmodconfig
xtensa defconfig
arc defconfig
arc allyesconfig
sh allmodconfig
sh allnoconfig
microblaze allnoconfig
mips allyesconfig
mips allnoconfig
mips allmodconfig
parisc allnoconfig
parisc defconfig
parisc allyesconfig
parisc allmodconfig
powerpc defconfig
powerpc allyesconfig
powerpc rhel-kconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a016-20200615
i386 randconfig-a015-20200614
i386 randconfig-a011-20200614
i386 randconfig-a014-20200614
i386 randconfig-a013-20200614
i386 randconfig-a016-20200614
i386 randconfig-a012-20200614
i386 randconfig-a015-20200615
i386 randconfig-a011-20200615
i386 randconfig-a014-20200615
i386 randconfig-a013-20200615
i386 randconfig-a012-20200615
riscv allyesconfig
riscv allnoconfig
riscv defconfig
riscv allmodconfig
s390 allyesconfig
s390 allnoconfig
s390 allmodconfig
s390 defconfig
sparc allyesconfig
sparc defconfig
sparc64 defconfig
sparc64 allnoconfig
sparc64 allyesconfig
sparc64 allmodconfig
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 rhel-7.6
x86_64 rhel-7.6-kselftests
x86_64 rhel-8.3
x86_64 kexec
x86_64 rhel
x86_64 rhel-7.2-clear
x86_64 lkp
x86_64 fedora-25
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-06-15 5:48 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=5ee70ba4.HhGBcpaXT2jVn6Dh%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).