From: kernel test robot <lkp@intel.com>
To: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: [bluetooth-next:master] BUILD SUCCESS 64692e12507b3efd71b4ff5596c9742d91f1ffe5
Date: Sun, 28 Jan 2024 10:56:09 +0800 [thread overview]
Message-ID: <202401281007.MNhPXeKB-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
branch HEAD: 64692e12507b3efd71b4ff5596c9742d91f1ffe5 Bluetooth: qca: Fix wrong event type for patch config command
elapsed time: 3206m
configs tested: 99
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
arc randconfig-001-20240128 gcc
arc randconfig-002-20240128 gcc
arc tb10x_defconfig gcc
arm randconfig-001-20240128 clang
arm randconfig-002-20240128 clang
arm randconfig-003-20240128 clang
arm randconfig-004-20240128 clang
arm64 randconfig-001-20240128 clang
arm64 randconfig-002-20240128 clang
arm64 randconfig-003-20240128 clang
arm64 randconfig-004-20240128 clang
csky randconfig-001-20240128 gcc
csky randconfig-002-20240128 gcc
hexagon allmodconfig clang
hexagon allyesconfig clang
hexagon randconfig-001-20240128 clang
hexagon randconfig-002-20240128 clang
i386 buildonly-randconfig-001-20240127 gcc
i386 buildonly-randconfig-002-20240127 gcc
i386 buildonly-randconfig-003-20240127 gcc
i386 buildonly-randconfig-004-20240127 gcc
i386 buildonly-randconfig-005-20240127 gcc
i386 buildonly-randconfig-006-20240127 gcc
i386 randconfig-001-20240127 gcc
i386 randconfig-002-20240127 gcc
i386 randconfig-003-20240127 gcc
i386 randconfig-004-20240127 gcc
i386 randconfig-005-20240127 gcc
i386 randconfig-006-20240127 gcc
i386 randconfig-011-20240127 clang
i386 randconfig-012-20240127 clang
i386 randconfig-013-20240127 clang
i386 randconfig-014-20240127 clang
i386 randconfig-015-20240127 clang
i386 randconfig-016-20240127 clang
loongarch allmodconfig gcc
loongarch randconfig-001-20240128 gcc
loongarch randconfig-002-20240128 gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
microblaze allmodconfig gcc
microblaze allyesconfig gcc
mips allyesconfig gcc
nios2 allmodconfig gcc
nios2 allyesconfig gcc
nios2 randconfig-001-20240128 gcc
nios2 randconfig-002-20240128 gcc
openrisc allnoconfig gcc
openrisc allyesconfig gcc
openrisc defconfig gcc
parisc allmodconfig gcc
parisc allnoconfig gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc randconfig-001-20240128 gcc
parisc randconfig-002-20240128 gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
powerpc randconfig-001-20240128 clang
powerpc randconfig-002-20240128 clang
powerpc randconfig-003-20240128 clang
powerpc64 randconfig-001-20240128 clang
powerpc64 randconfig-002-20240128 clang
powerpc64 randconfig-003-20240128 clang
riscv allmodconfig gcc
riscv allnoconfig clang
riscv allyesconfig gcc
riscv defconfig gcc
riscv randconfig-001-20240128 clang
riscv randconfig-002-20240128 clang
riscv rv32_defconfig clang
s390 allmodconfig gcc
s390 allnoconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-001-20240128 gcc
s390 randconfig-002-20240128 gcc
sh allmodconfig gcc
sh allnoconfig gcc
sh allyesconfig gcc
sh defconfig gcc
sh randconfig-001-20240128 gcc
sh randconfig-002-20240128 gcc
sparc allmodconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 defconfig gcc
sparc64 randconfig-001-20240128 gcc
sparc64 randconfig-002-20240128 gcc
um allmodconfig clang
um allnoconfig clang
um allyesconfig clang
um defconfig gcc
um i386_defconfig gcc
um randconfig-001-20240128 clang
um randconfig-002-20240128 clang
um x86_64_defconfig gcc
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-28 2: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=202401281007.MNhPXeKB-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.dentz@intel.com \
/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).