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 dfa48dfca48ec34b44686d8c4a59e7aaa25beadd
Date: Sat, 08 Mar 2025 23:38:19 +0800 [thread overview]
Message-ID: <202503082313.620FPsGr-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
branch HEAD: dfa48dfca48ec34b44686d8c4a59e7aaa25beadd Bluetooth: btintel_pci: Fix build warning
elapsed time: 1446m
configs tested: 64
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arc randconfig-001-20250308 gcc-13.2.0
arc randconfig-002-20250308 gcc-13.2.0
arm randconfig-001-20250308 gcc-14.2.0
arm randconfig-002-20250308 gcc-14.2.0
arm randconfig-003-20250308 gcc-14.2.0
arm randconfig-004-20250308 gcc-14.2.0
arm64 randconfig-001-20250308 gcc-14.2.0
arm64 randconfig-002-20250308 gcc-14.2.0
arm64 randconfig-003-20250308 clang-16
arm64 randconfig-004-20250308 gcc-14.2.0
csky randconfig-001-20250308 gcc-14.2.0
csky randconfig-002-20250308 gcc-14.2.0
hexagon randconfig-001-20250308 clang-19
hexagon randconfig-002-20250308 clang-21
i386 buildonly-randconfig-001-20250308 gcc-12
i386 buildonly-randconfig-002-20250308 gcc-11
i386 buildonly-randconfig-003-20250308 clang-19
i386 buildonly-randconfig-004-20250308 clang-19
i386 buildonly-randconfig-005-20250308 clang-19
i386 buildonly-randconfig-006-20250308 gcc-12
loongarch randconfig-001-20250308 gcc-14.2.0
loongarch randconfig-002-20250308 gcc-14.2.0
nios2 randconfig-001-20250308 gcc-14.2.0
nios2 randconfig-002-20250308 gcc-14.2.0
openrisc allnoconfig gcc-14.2.0
parisc allnoconfig gcc-14.2.0
parisc randconfig-001-20250308 gcc-14.2.0
parisc randconfig-002-20250308 gcc-14.2.0
powerpc allnoconfig gcc-14.2.0
powerpc randconfig-001-20250308 clang-18
powerpc randconfig-002-20250308 gcc-14.2.0
powerpc randconfig-003-20250308 gcc-14.2.0
powerpc64 randconfig-001-20250308 gcc-14.2.0
powerpc64 randconfig-003-20250308 clang-21
riscv allnoconfig gcc-14.2.0
riscv randconfig-001-20250308 clang-21
riscv randconfig-002-20250308 gcc-14.2.0
s390 allmodconfig clang-19
s390 allnoconfig clang-15
s390 allyesconfig gcc-14.2.0
s390 randconfig-001-20250308 clang-19
s390 randconfig-002-20250308 clang-17
sh allmodconfig gcc-14.2.0
sh allyesconfig gcc-14.2.0
sh randconfig-001-20250308 gcc-14.2.0
sh randconfig-002-20250308 gcc-14.2.0
sparc allmodconfig gcc-14.2.0
sparc randconfig-001-20250308 gcc-14.2.0
sparc randconfig-002-20250308 gcc-14.2.0
sparc64 randconfig-001-20250308 gcc-14.2.0
sparc64 randconfig-002-20250308 gcc-14.2.0
um allnoconfig clang-18
um randconfig-001-20250308 gcc-12
um randconfig-002-20250308 gcc-12
x86_64 allnoconfig clang-19
x86_64 buildonly-randconfig-001-20250308 gcc-12
x86_64 buildonly-randconfig-002-20250308 clang-19
x86_64 buildonly-randconfig-003-20250308 gcc-12
x86_64 buildonly-randconfig-004-20250308 clang-19
x86_64 buildonly-randconfig-005-20250308 clang-19
x86_64 buildonly-randconfig-006-20250308 clang-19
x86_64 defconfig gcc-11
xtensa randconfig-001-20250308 gcc-14.2.0
xtensa randconfig-002-20250308 gcc-14.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-03-08 15: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=202503082313.620FPsGr-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 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.