From: kernel test robot <lkp@intel.com>
To: "Krzysztof Wilczyński " <kwilczynski@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: [pci:dpc] BUILD SUCCESS b198499c7d2508a76243b98e7cca992f6fd2b7f7
Date: Fri, 17 Jan 2025 02:32:22 +0800 [thread overview]
Message-ID: <202501170216.2M35AtCa-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git dpc
branch HEAD: b198499c7d2508a76243b98e7cca992f6fd2b7f7 PCI/DPC: Quirk PIO log size for Intel Raptor Lake-P
elapsed time: 1455m
configs tested: 65
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-14.2.0
arc allnoconfig gcc-13.2.0
arc randconfig-001-20250116 gcc-13.2.0
arc randconfig-002-20250116 gcc-13.2.0
arm allnoconfig clang-17
arm randconfig-001-20250116 gcc-14.2.0
arm randconfig-002-20250116 clang-15
arm randconfig-003-20250116 gcc-14.2.0
arm randconfig-004-20250116 gcc-14.2.0
arm64 allnoconfig gcc-14.2.0
arm64 randconfig-001-20250116 gcc-14.2.0
arm64 randconfig-002-20250116 gcc-14.2.0
arm64 randconfig-003-20250116 clang-15
arm64 randconfig-004-20250116 clang-20
csky allnoconfig gcc-14.2.0
csky randconfig-001-20250116 gcc-14.2.0
csky randconfig-002-20250116 gcc-14.2.0
hexagon allnoconfig clang-20
hexagon randconfig-001-20250116 clang-20
hexagon randconfig-002-20250116 clang-20
i386 buildonly-randconfig-001-20250116 clang-19
i386 buildonly-randconfig-002-20250116 clang-19
i386 buildonly-randconfig-003-20250116 clang-19
i386 buildonly-randconfig-004-20250116 clang-19
i386 buildonly-randconfig-005-20250116 clang-19
i386 buildonly-randconfig-006-20250116 clang-19
loongarch allnoconfig gcc-14.2.0
loongarch randconfig-001-20250116 gcc-14.2.0
loongarch randconfig-002-20250116 gcc-14.2.0
nios2 randconfig-001-20250116 gcc-14.2.0
nios2 randconfig-002-20250116 gcc-14.2.0
parisc randconfig-001-20250116 gcc-14.2.0
parisc randconfig-002-20250116 gcc-14.2.0
powerpc randconfig-001-20250116 clang-20
powerpc randconfig-002-20250116 gcc-14.2.0
powerpc randconfig-003-20250116 clang-20
powerpc64 randconfig-001-20250116 clang-19
powerpc64 randconfig-002-20250116 clang-20
powerpc64 randconfig-003-20250116 clang-15
riscv randconfig-001-20250116 gcc-14.2.0
riscv randconfig-002-20250116 gcc-14.2.0
s390 allmodconfig clang-19
s390 allyesconfig gcc-14.2.0
s390 randconfig-001-20250116 gcc-14.2.0
s390 randconfig-002-20250116 clang-18
sh allmodconfig gcc-14.2.0
sh allyesconfig gcc-14.2.0
sh randconfig-001-20250116 gcc-14.2.0
sh randconfig-002-20250116 gcc-14.2.0
sparc randconfig-001-20250116 gcc-14.2.0
sparc randconfig-002-20250116 gcc-14.2.0
sparc64 randconfig-001-20250116 gcc-14.2.0
sparc64 randconfig-002-20250116 gcc-14.2.0
um randconfig-001-20250116 clang-19
um randconfig-002-20250116 gcc-12
x86_64 allnoconfig clang-19
x86_64 buildonly-randconfig-001-20250116 gcc-12
x86_64 buildonly-randconfig-002-20250116 gcc-12
x86_64 buildonly-randconfig-003-20250116 gcc-12
x86_64 buildonly-randconfig-004-20250116 clang-19
x86_64 buildonly-randconfig-005-20250116 clang-19
x86_64 buildonly-randconfig-006-20250116 clang-19
x86_64 defconfig gcc-11
xtensa randconfig-001-20250116 gcc-14.2.0
xtensa randconfig-002-20250116 gcc-14.2.0
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-16 18:32 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=202501170216.2M35AtCa-lkp@intel.com \
--to=lkp@intel.com \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.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.