From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:irq/urgent] BUILD SUCCESS b184c8c2889ceef0a137c7d0567ef9fe3d92276e
Date: Fri, 26 Jan 2024 09:32:49 +0800 [thread overview]
Message-ID: <202401260946.Y8GxfBhs-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
branch HEAD: b184c8c2889ceef0a137c7d0567ef9fe3d92276e genirq: Initialize resend_node hlist for all interrupt descriptors
elapsed time: 1864m
configs tested: 89
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha defconfig gcc
arc allmodconfig gcc
arc allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arm allmodconfig gcc
arm allnoconfig gcc
arm allyesconfig gcc
arm64 allnoconfig gcc
csky allmodconfig gcc
csky allyesconfig gcc
i386 allmodconfig clang
i386 allnoconfig clang
i386 allyesconfig clang
i386 buildonly-randconfig-001-20240125 gcc
i386 buildonly-randconfig-002-20240125 gcc
i386 buildonly-randconfig-003-20240125 gcc
i386 buildonly-randconfig-004-20240125 gcc
i386 buildonly-randconfig-005-20240125 gcc
i386 buildonly-randconfig-006-20240125 gcc
i386 defconfig gcc
i386 randconfig-001-20240125 gcc
i386 randconfig-002-20240125 gcc
i386 randconfig-003-20240125 gcc
i386 randconfig-004-20240125 gcc
i386 randconfig-005-20240125 gcc
i386 randconfig-006-20240125 gcc
i386 randconfig-011-20240125 clang
i386 randconfig-012-20240125 clang
i386 randconfig-013-20240125 clang
i386 randconfig-014-20240125 clang
i386 randconfig-015-20240125 clang
i386 randconfig-016-20240125 clang
loongarch allmodconfig gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
microblaze allmodconfig gcc
microblaze allyesconfig gcc
openrisc allnoconfig gcc
openrisc allyesconfig gcc
openrisc defconfig gcc
parisc allmodconfig gcc
parisc allnoconfig gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig clang
powerpc allnoconfig gcc
powerpc allyesconfig clang
riscv allmodconfig gcc
riscv allnoconfig clang
riscv allyesconfig gcc
riscv defconfig gcc
s390 allnoconfig gcc
s390 defconfig gcc
sh allnoconfig gcc
sh defconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 defconfig gcc
um allmodconfig clang
um allnoconfig clang
um defconfig gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig clang
x86_64 buildonly-randconfig-001-20240126 clang
x86_64 buildonly-randconfig-002-20240126 clang
x86_64 buildonly-randconfig-003-20240126 clang
x86_64 buildonly-randconfig-004-20240126 clang
x86_64 buildonly-randconfig-005-20240126 clang
x86_64 buildonly-randconfig-006-20240126 clang
x86_64 defconfig gcc
x86_64 randconfig-001-20240126 gcc
x86_64 randconfig-002-20240126 gcc
x86_64 randconfig-003-20240126 gcc
x86_64 randconfig-004-20240126 gcc
x86_64 randconfig-005-20240126 gcc
x86_64 randconfig-006-20240126 gcc
x86_64 randconfig-011-20240126 clang
x86_64 randconfig-012-20240126 clang
x86_64 randconfig-013-20240126 clang
x86_64 randconfig-014-20240126 clang
x86_64 randconfig-016-20240126 clang
x86_64 randconfig-071-20240126 clang
x86_64 rhel-8.3-rust clang
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-26 1:33 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=202401260946.Y8GxfBhs-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
all inboxes | Powered by JetHome®