From: kernel test robot <lkp@intel.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org
Subject: [driver-core:debugfs_cleanup] BUILD SUCCESS 065b4f86f7cfb6c95cbe4d5d81ae1b13d753b5f6
Date: Sat, 17 Oct 2020 03:36:03 +0800 [thread overview]
Message-ID: <5f89f623.J1YG5kSEYTbbY03w%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git debugfs_cleanup
branch HEAD: 065b4f86f7cfb6c95cbe4d5d81ae1b13d753b5f6 debugfs: remove return value of debugfs_create_devm_seqfile()
elapsed time: 722m
configs tested: 105
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm defconfig
arm64 allyesconfig
arm64 defconfig
arm allyesconfig
arm allmodconfig
arm at91_dt_defconfig
mips rb532_defconfig
powerpc64 alldefconfig
arm mps2_defconfig
h8300 edosk2674_defconfig
mips mtx1_defconfig
arm aspeed_g5_defconfig
arm exynos_defconfig
ia64 generic_defconfig
arm xcep_defconfig
arm tango4_defconfig
powerpc mpc85xx_cds_defconfig
mips cu1830-neo_defconfig
powerpc mpc832x_rdb_defconfig
arm sama5_defconfig
arm mv78xx0_defconfig
powerpc tqm8540_defconfig
arm multi_v7_defconfig
arm socfpga_defconfig
powerpc pasemi_defconfig
arm palmz72_defconfig
powerpc currituck_defconfig
powerpc mpc836x_mds_defconfig
powerpc cell_defconfig
sh sh7785lcr_defconfig
sh sh7757lcr_defconfig
openrisc or1ksim_defconfig
h8300 allyesconfig
powerpc motionpro_defconfig
sh se7724_defconfig
m68k apollo_defconfig
powerpc mpc7448_hpc2_defconfig
riscv defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20201016
i386 randconfig-a006-20201016
i386 randconfig-a001-20201016
i386 randconfig-a003-20201016
i386 randconfig-a004-20201016
i386 randconfig-a002-20201016
x86_64 randconfig-a016-20201016
x86_64 randconfig-a012-20201016
x86_64 randconfig-a015-20201016
x86_64 randconfig-a013-20201016
x86_64 randconfig-a014-20201016
x86_64 randconfig-a011-20201016
i386 randconfig-a016-20201016
i386 randconfig-a013-20201016
i386 randconfig-a015-20201016
i386 randconfig-a011-20201016
i386 randconfig-a012-20201016
i386 randconfig-a014-20201016
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a004-20201016
x86_64 randconfig-a002-20201016
x86_64 randconfig-a006-20201016
x86_64 randconfig-a001-20201016
x86_64 randconfig-a005-20201016
x86_64 randconfig-a003-20201016
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
reply other threads:[~2020-10-16 19:36 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=5f89f623.J1YG5kSEYTbbY03w%lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).