From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:irq/core] BUILD SUCCESS 863bae1fbcfa0420e5f51389218a9532542aa00f
Date: Mon, 12 Oct 2020 17:56:32 +0800 [thread overview]
Message-ID: <5f842850.gWtDZT/Fezm5ygj2%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/core
branch HEAD: 863bae1fbcfa0420e5f51389218a9532542aa00f Merge tag 'irqchip-5.10' of git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms into irq/core
elapsed time: 721m
configs tested: 109
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
powerpc tqm8541_defconfig
mips jmr3927_defconfig
m68k bvme6000_defconfig
arc nps_defconfig
arm tango4_defconfig
mips maltasmvp_defconfig
i386 allyesconfig
sh se7206_defconfig
powerpc tqm5200_defconfig
mips bigsur_defconfig
mips bmips_be_defconfig
um kunit_defconfig
arm stm32_defconfig
xtensa smp_lx200_defconfig
x86_64 alldefconfig
arm xcep_defconfig
xtensa defconfig
riscv nommu_k210_defconfig
sh rsk7269_defconfig
riscv allmodconfig
s390 defconfig
arc axs103_smp_defconfig
powerpc linkstation_defconfig
mips maltaup_xpa_defconfig
i386 defconfig
sh sh7785lcr_defconfig
arc nsimosci_hs_defconfig
powerpc mpc7448_hpc2_defconfig
sh sh2007_defconfig
arm imote2_defconfig
arm ebsa110_defconfig
arm vexpress_defconfig
arm badge4_defconfig
mips ath79_defconfig
mips omega2p_defconfig
c6x dsk6455_defconfig
arm lubbock_defconfig
arm multi_v4t_defconfig
powerpc mpc837x_mds_defconfig
sh ecovec24_defconfig
ia64 allmodconfig
ia64 defconfig
ia64 allyesconfig
m68k allmodconfig
m68k defconfig
m68k allyesconfig
nios2 defconfig
arc allyesconfig
nds32 allnoconfig
c6x allyesconfig
nds32 defconfig
nios2 allyesconfig
csky defconfig
alpha defconfig
alpha allyesconfig
xtensa allyesconfig
h8300 allyesconfig
arc defconfig
sh allmodconfig
parisc defconfig
s390 allyesconfig
parisc allyesconfig
sparc allyesconfig
sparc defconfig
mips allyesconfig
mips allmodconfig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
i386 randconfig-a005-20201012
i386 randconfig-a006-20201012
i386 randconfig-a001-20201012
i386 randconfig-a003-20201012
i386 randconfig-a004-20201012
i386 randconfig-a002-20201012
x86_64 randconfig-a016-20201012
x86_64 randconfig-a015-20201012
x86_64 randconfig-a012-20201012
x86_64 randconfig-a013-20201012
x86_64 randconfig-a014-20201012
x86_64 randconfig-a011-20201012
i386 randconfig-a016-20201012
i386 randconfig-a015-20201012
i386 randconfig-a013-20201012
i386 randconfig-a012-20201012
i386 randconfig-a011-20201012
i386 randconfig-a014-20201012
riscv allyesconfig
riscv nommu_virt_defconfig
riscv allnoconfig
riscv defconfig
riscv rv32_defconfig
x86_64 rhel
x86_64 allyesconfig
x86_64 rhel-7.6-kselftests
x86_64 defconfig
x86_64 rhel-8.3
x86_64 kexec
clang tested configs:
x86_64 randconfig-a004-20201012
x86_64 randconfig-a002-20201012
x86_64 randconfig-a006-20201012
x86_64 randconfig-a001-20201012
x86_64 randconfig-a003-20201012
x86_64 randconfig-a005-20201012
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2020-10-12 9: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=5f842850.gWtDZT/Fezm5ygj2%lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 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).