From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:x86/urgent] BUILD SUCCESS d00dd2f2645dca04cf399d8fc692f3f69b6dd996
Date: Tue, 03 Jan 2023 14:07:30 +0800 [thread overview]
Message-ID: <63b3c622.J6Rrl0ByF0IiwgZd%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
branch HEAD: d00dd2f2645dca04cf399d8fc692f3f69b6dd996 x86/kexec: Fix double-free of elf header buffer
elapsed time: 723m
configs tested: 37
configs skipped: 74
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
x86_64 rhel-8.3-bpf
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-kvm
i386 randconfig-a004-20230102
i386 randconfig-a003-20230102
i386 randconfig-a001-20230102
x86_64 defconfig
i386 randconfig-a002-20230102
i386 defconfig
i386 randconfig-a005-20230102
i386 randconfig-a006-20230102
x86_64 rhel-8.3
x86_64 randconfig-a001-20230102
x86_64 randconfig-a004-20230102
x86_64 randconfig-a002-20230102
x86_64 randconfig-a003-20230102
x86_64 randconfig-a005-20230102
x86_64 randconfig-a006-20230102
x86_64 allyesconfig
i386 allyesconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
x86_64 allnoconfig
clang tested configs:
x86_64 rhel-8.3-rust
x86_64 randconfig-a011-20230102
x86_64 randconfig-a014-20230102
x86_64 randconfig-a012-20230102
x86_64 randconfig-a013-20230102
i386 randconfig-a011-20230102
x86_64 randconfig-a015-20230102
x86_64 randconfig-a016-20230102
i386 randconfig-a014-20230102
i386 randconfig-a013-20230102
i386 randconfig-a012-20230102
i386 randconfig-a015-20230102
i386 randconfig-a016-20230102
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2023-01-03 6:08 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=63b3c622.J6Rrl0ByF0IiwgZd%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®