From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/sgx] BUILD SUCCESS 1e327963cfab0e02eeeb0331178d6c353c959cd6
Date: Wed, 14 Jun 2023 11:00:00 +0800 [thread overview]
Message-ID: <202306141058.6lo6wBDX-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/sgx
branch HEAD: 1e327963cfab0e02eeeb0331178d6c353c959cd6 x86/sgx: Avoid using iterator after loop in sgx_mmu_notifier_release()
elapsed time: 724m
configs tested: 88
configs skipped: 98
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
alpha defconfig gcc
arc alldefconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm imx_v4_v5_defconfig clang
arm randconfig-r046-20230612 clang
arm64 allyesconfig gcc
arm64 defconfig gcc
csky defconfig gcc
csky randconfig-r023-20230612 gcc
csky randconfig-r035-20230612 gcc
csky randconfig-r036-20230612 gcc
hexagon randconfig-r041-20230612 clang
hexagon randconfig-r045-20230612 clang
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i001-20230612 clang
i386 randconfig-i002-20230612 clang
i386 randconfig-i003-20230612 clang
i386 randconfig-i004-20230612 clang
i386 randconfig-i005-20230612 clang
i386 randconfig-i006-20230612 clang
i386 randconfig-i011-20230612 gcc
i386 randconfig-i012-20230612 gcc
i386 randconfig-i013-20230612 gcc
i386 randconfig-i014-20230612 gcc
i386 randconfig-i015-20230612 gcc
i386 randconfig-i016-20230612 gcc
i386 randconfig-r035-20230612 clang
m68k allmodconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
microblaze randconfig-r031-20230612 gcc
mips allmodconfig gcc
mips allyesconfig gcc
nios2 buildonly-randconfig-r001-20230612 gcc
nios2 buildonly-randconfig-r005-20230612 gcc
nios2 defconfig gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc randconfig-r022-20230612 gcc
parisc randconfig-r034-20230612 gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc ppc6xx_defconfig gcc
powerpc randconfig-r024-20230612 gcc
powerpc sequoia_defconfig gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv allyesconfig gcc
riscv defconfig gcc
riscv randconfig-r006-20230612 clang
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
sh allmodconfig gcc
sh buildonly-randconfig-r003-20230612 gcc
sh se7724_defconfig gcc
sparc allyesconfig gcc
sparc defconfig gcc
sparc sparc32_defconfig gcc
sparc64 buildonly-randconfig-r006-20230612 gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a001-20230612 clang
x86_64 randconfig-a002-20230612 clang
x86_64 randconfig-a003-20230612 clang
x86_64 randconfig-a004-20230612 clang
x86_64 randconfig-a005-20230612 clang
x86_64 randconfig-a006-20230612 clang
x86_64 randconfig-a011-20230612 gcc
x86_64 randconfig-a012-20230612 gcc
x86_64 randconfig-a013-20230612 gcc
x86_64 randconfig-a014-20230612 gcc
x86_64 randconfig-a015-20230612 gcc
x86_64 randconfig-a016-20230612 gcc
x86_64 randconfig-r005-20230612 clang
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
xtensa randconfig-r033-20230612 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-14 3:00 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=202306141058.6lo6wBDX-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®