From: kernel test robot <lkp@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: [bluetooth-next:master] BUILD SUCCESS 35191a0fe986bacf69bd842de81119dca7970f11
Date: Wed, 01 Sep 2021 10:17:45 +0800 [thread overview]
Message-ID: <612ee2c9.r3m6I+dGQSfm2DRd%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
branch HEAD: 35191a0fe986bacf69bd842de81119dca7970f11 Bluetooth: btintel: Read boot address irrespective of controller mode
elapsed time: 729m
configs tested: 103
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
i386 randconfig-c001-20210831
powerpc redwood_defconfig
sparc alldefconfig
arc tb10x_defconfig
riscv nommu_k210_sdcard_defconfig
arc nsimosci_hs_defconfig
arm trizeps4_defconfig
arm milbeaut_m10v_defconfig
powerpc tqm8560_defconfig
arm viper_defconfig
mips mtx1_defconfig
powerpc mpc512x_defconfig
arc vdk_hs38_defconfig
m68k mvme16x_defconfig
sh j2_defconfig
arm versatile_defconfig
sh shmin_defconfig
x86_64 allnoconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
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
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a005-20210831
x86_64 randconfig-a001-20210831
x86_64 randconfig-a003-20210831
x86_64 randconfig-a002-20210831
x86_64 randconfig-a004-20210831
x86_64 randconfig-a006-20210831
i386 randconfig-a005-20210831
i386 randconfig-a002-20210831
i386 randconfig-a003-20210831
i386 randconfig-a006-20210831
i386 randconfig-a004-20210831
i386 randconfig-a001-20210831
riscv nommu_k210_defconfig
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
riscv allmodconfig
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
i386 randconfig-c001-20210831
s390 randconfig-c005-20210831
riscv randconfig-c006-20210831
powerpc randconfig-c003-20210831
mips randconfig-c004-20210831
arm randconfig-c002-20210831
x86_64 randconfig-c007-20210831
x86_64 randconfig-a014-20210831
x86_64 randconfig-a015-20210831
x86_64 randconfig-a013-20210831
x86_64 randconfig-a016-20210831
x86_64 randconfig-a012-20210831
x86_64 randconfig-a011-20210831
i386 randconfig-a016-20210831
i386 randconfig-a011-20210831
i386 randconfig-a015-20210831
i386 randconfig-a014-20210831
i386 randconfig-a012-20210831
i386 randconfig-a013-20210831
s390 randconfig-r044-20210831
hexagon randconfig-r041-20210831
hexagon randconfig-r045-20210831
riscv randconfig-r042-20210831
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2021-09-01 2:18 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=612ee2c9.r3m6I+dGQSfm2DRd%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.