From: kernel test robot <lkp@intel.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: [geert-m68k:for-v6.7] BUILD SUCCESS 0c316da2164c5980ad4b3da5d8efbb6019b5b18c
Date: Tue, 26 Sep 2023 08:32:44 +0800 [thread overview]
Message-ID: <202309260841.t1nKJqiU-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-v6.7
branch HEAD: 0c316da2164c5980ad4b3da5d8efbb6019b5b18c m68k: Replace GPL 2.0+ README.legal boilerplate with SPDX
elapsed time: 734m
configs tested: 88
configs skipped: 159
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc
alpha allyesconfig gcc
alpha defconfig gcc
arc randconfig-001-20230926 gcc
arm allmodconfig gcc
arm allnoconfig gcc
arm allyesconfig gcc
arm assabet_defconfig gcc
arm defconfig gcc
arm multi_v7_defconfig gcc
csky allmodconfig gcc
csky allnoconfig gcc
csky allyesconfig gcc
csky defconfig gcc
i386 allmodconfig gcc
i386 allnoconfig gcc
i386 allyesconfig gcc
i386 buildonly-randconfig-001-20230926 gcc
i386 buildonly-randconfig-002-20230926 gcc
i386 buildonly-randconfig-003-20230926 gcc
i386 buildonly-randconfig-004-20230926 gcc
i386 buildonly-randconfig-005-20230926 gcc
i386 buildonly-randconfig-006-20230926 gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-001-20230926 gcc
i386 randconfig-002-20230926 gcc
i386 randconfig-003-20230926 gcc
i386 randconfig-004-20230926 gcc
i386 randconfig-005-20230926 gcc
i386 randconfig-006-20230926 gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch allyesconfig gcc
loongarch defconfig gcc
loongarch randconfig-001-20230926 gcc
m68k allmodconfig gcc
m68k allnoconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
microblaze allmodconfig gcc
microblaze allnoconfig gcc
microblaze allyesconfig gcc
microblaze defconfig gcc
mips bcm63xx_defconfig clang
mips maltasmvp_defconfig gcc
nios2 allmodconfig gcc
nios2 allnoconfig gcc
nios2 allyesconfig gcc
nios2 defconfig gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv allyesconfig gcc
riscv defconfig gcc
riscv randconfig-001-20230926 gcc
riscv rv32_defconfig gcc
s390 randconfig-001-20230926 gcc
sh allmodconfig gcc
sh allnoconfig gcc
sh allyesconfig gcc
sh defconfig gcc
sparc64 allmodconfig gcc
sparc64 allyesconfig gcc
sparc64 defconfig gcc
um defconfig gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 buildonly-randconfig-001-20230926 gcc
x86_64 buildonly-randconfig-002-20230926 gcc
x86_64 buildonly-randconfig-003-20230926 gcc
x86_64 buildonly-randconfig-004-20230926 gcc
x86_64 buildonly-randconfig-005-20230926 gcc
x86_64 buildonly-randconfig-006-20230926 gcc
x86_64 randconfig-001-20230926 gcc
x86_64 randconfig-002-20230926 gcc
x86_64 randconfig-003-20230926 gcc
x86_64 randconfig-004-20230926 gcc
x86_64 randconfig-005-20230926 gcc
x86_64 randconfig-006-20230926 gcc
x86_64 randconfig-071-20230926 gcc
x86_64 randconfig-072-20230926 gcc
x86_64 randconfig-073-20230926 gcc
x86_64 randconfig-074-20230926 gcc
x86_64 randconfig-075-20230926 gcc
x86_64 randconfig-076-20230926 gcc
xtensa allnoconfig gcc
xtensa allyesconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-26 0: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=202309260841.t1nKJqiU-lkp@intel.com \
--to=lkp@intel.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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 read-only IMAP folder(s) and NNTP newsgroup(s).