From: kernel test robot <lkp@intel.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [powerpc:next-test] BUILD SUCCESS b059dfc41139ee194c9127b89dbea02afa409443
Date: Tue, 18 Jul 2023 11:30:26 +0800 [thread overview]
Message-ID: <202307181124.VgDvtGZB-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next-test
branch HEAD: b059dfc41139ee194c9127b89dbea02afa409443 powerpc/64: Enable accelerated crypto algorithms in defconfig
elapsed time: 796m
configs tested: 38
configs skipped: 145
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
arc allyesconfig gcc
arm pxa910_defconfig gcc
arm realview_defconfig gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
m68k m5272c3_defconfig gcc
m68k stmark2_defconfig gcc
mips allmodconfig gcc
powerpc akebono_defconfig clang
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc asp8347_defconfig gcc
powerpc eiger_defconfig gcc
powerpc maple_defconfig gcc
powerpc ppc40x_defconfig gcc
powerpc ps3_defconfig gcc
powerpc randconfig-r023-20230717 gcc
powerpc randconfig-r026-20230717 gcc
sh lboxre2_defconfig gcc
sh rts7751r2dplus_defconfig gcc
sh sdk7786_defconfig gcc
sh sh7724_generic_defconfig gcc
um allmodconfig clang
um allnoconfig clang
um allyesconfig clang
x86_64 allyesconfig gcc
x86_64 randconfig-x002-20230717 gcc
x86_64 randconfig-x003-20230717 gcc
x86_64 randconfig-x004-20230717 gcc
x86_64 randconfig-x005-20230717 gcc
x86_64 randconfig-x006-20230717 gcc
x86_64 randconfig-x011-20230717 clang
x86_64 randconfig-x012-20230717 clang
x86_64 randconfig-x013-20230717 clang
x86_64 randconfig-x014-20230717 clang
x86_64 randconfig-x015-20230717 clang
x86_64 randconfig-x016-20230717 clang
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-18 3: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=202307181124.VgDvtGZB-lkp@intel.com \
--to=lkp@intel.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).