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 47214aa268369347f1e4ae5a3fb2aabb559fc3b2
Date: Tue, 04 May 2021 01:38:37 +0800 [thread overview]
Message-ID: <6090351d.xIrxtGQ+XOLQ1Wz2%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git debugfs_cleanup
branch HEAD: 47214aa268369347f1e4ae5a3fb2aabb559fc3b2 debugfs: remove return value of debugfs_create_bool()
elapsed time: 720m
configs tested: 100
configs skipped: 2
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
x86_64 allyesconfig
riscv allyesconfig
openrisc alldefconfig
powerpc powernv_defconfig
xtensa defconfig
arm oxnas_v6_defconfig
arm orion5x_defconfig
sh se7721_defconfig
powerpc adder875_defconfig
powerpc mpc832x_mds_defconfig
um i386_defconfig
powerpc holly_defconfig
arm milbeaut_m10v_defconfig
powerpc gamecube_defconfig
m68k m5208evb_defconfig
powerpc obs600_defconfig
riscv nommu_virt_defconfig
powerpc katmai_defconfig
powerpc skiroot_defconfig
arm trizeps4_defconfig
powerpc pcm030_defconfig
arm imx_v6_v7_defconfig
mips mpc30x_defconfig
mips bcm47xx_defconfig
powerpc mpc83xx_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
s390 allmodconfig
parisc allyesconfig
s390 defconfig
i386 allyesconfig
sparc allyesconfig
sparc defconfig
i386 defconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a001-20210503
x86_64 randconfig-a005-20210503
x86_64 randconfig-a003-20210503
x86_64 randconfig-a002-20210503
x86_64 randconfig-a006-20210503
x86_64 randconfig-a004-20210503
i386 randconfig-a003-20210503
i386 randconfig-a006-20210503
i386 randconfig-a001-20210503
i386 randconfig-a005-20210503
i386 randconfig-a004-20210503
i386 randconfig-a002-20210503
i386 randconfig-a013-20210503
i386 randconfig-a015-20210503
i386 randconfig-a016-20210503
i386 randconfig-a014-20210503
i386 randconfig-a011-20210503
i386 randconfig-a012-20210503
riscv nommu_k210_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
um allmodconfig
um allnoconfig
um allyesconfig
um defconfig
x86_64 rhel-8.3-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kbuiltin
x86_64 kexec
clang tested configs:
x86_64 randconfig-a014-20210503
x86_64 randconfig-a015-20210503
x86_64 randconfig-a012-20210503
x86_64 randconfig-a011-20210503
x86_64 randconfig-a013-20210503
x86_64 randconfig-a016-20210503
---
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:[~2021-05-03 17:39 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=6090351d.xIrxtGQ+XOLQ1Wz2%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 read-only IMAP folder(s) and NNTP newsgroup(s).