public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "x86-ml" <x86@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: [tip:perf/urgent] BUILD SUCCESS 50a53b60e141d7e31368a87e222e4dd5597bd4ae
Date: Sun, 23 Mar 2025 16:38:55 +0800	[thread overview]
Message-ID: <202503231650.ZPj02Ox0-lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf/urgent
branch HEAD: 50a53b60e141d7e31368a87e222e4dd5597bd4ae  perf/amd/ibs: Prevent leaking sensitive data to userspace

elapsed time: 1444m

configs tested: 19
configs skipped: 127

The following configs have been built successfully.
More configs may be tested in the coming days.

tested configs:
i386                         allmodconfig    gcc-12
i386                          allnoconfig    gcc-12
i386                         allyesconfig    gcc-12
i386    buildonly-randconfig-001-20250322    clang-20
i386    buildonly-randconfig-002-20250322    gcc-12
i386    buildonly-randconfig-003-20250322    gcc-12
i386    buildonly-randconfig-004-20250322    clang-20
i386    buildonly-randconfig-005-20250322    clang-20
i386    buildonly-randconfig-006-20250322    clang-20
i386                            defconfig    clang-20
x86_64                        allnoconfig    clang-20
x86_64                       allyesconfig    clang-20
x86_64  buildonly-randconfig-001-20250322    clang-20
x86_64  buildonly-randconfig-002-20250322    clang-20
x86_64  buildonly-randconfig-003-20250322    clang-20
x86_64  buildonly-randconfig-004-20250322    gcc-12
x86_64  buildonly-randconfig-005-20250322    clang-20
x86_64  buildonly-randconfig-006-20250322    gcc-12
x86_64                          defconfig    gcc-11

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-03-23  8:39 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=202503231650.ZPj02Ox0-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