linux-m68k.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.17] BUILD SUCCESS c8995932db2bad6fa093ac64dbaf7a3e8870eafa
Date: Mon, 07 Jul 2025 07:04:09 +0800	[thread overview]
Message-ID: <202507070757.U9X4Pn4I-lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k.git for-v6.17
branch HEAD: c8995932db2bad6fa093ac64dbaf7a3e8870eafa  m68k: mac: Improve clocksource driver commentary

elapsed time: 722m

configs tested: 48
configs skipped: 128

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

tested configs:
alpha                   allnoconfig    clang-21
arc                     allnoconfig    clang-21
arm                     allnoconfig    clang-21
arm                gemini_defconfig    clang-21
arm                 omap1_defconfig    clang-21
arm64                   allnoconfig    clang-21
csky                    allnoconfig    clang-21
hexagon                 allnoconfig    clang-21
i386        randconfig-001-20250707    gcc-12
i386        randconfig-002-20250707    gcc-12
i386        randconfig-003-20250707    gcc-12
i386        randconfig-004-20250707    gcc-12
i386        randconfig-005-20250707    gcc-12
i386        randconfig-006-20250707    gcc-12
i386        randconfig-007-20250707    gcc-12
i386        randconfig-011-20250707    gcc-12
i386        randconfig-012-20250707    gcc-12
i386        randconfig-013-20250707    gcc-12
i386        randconfig-014-20250707    gcc-12
i386        randconfig-015-20250707    gcc-12
i386        randconfig-016-20250707    gcc-12
i386        randconfig-017-20250707    gcc-12
loongarch              allmodconfig    clang-19
loongarch               allnoconfig    clang-21
m68k                   allmodconfig    gcc-15.1.0
m68k                    allnoconfig    gcc-15.1.0
m68k                   allyesconfig    gcc-15.1.0
m68k             m5475evb_defconfig    clang-21
m68k                 virt_defconfig    clang-21
microblaze             allmodconfig    gcc-15.1.0
microblaze              allnoconfig    gcc-15.1.0
microblaze             allyesconfig    gcc-15.1.0
microblaze                defconfig    gcc-15.1.0
mips                    allnoconfig    gcc-15.1.0
mips            maltaaprp_defconfig    clang-21
nios2                   allnoconfig    gcc-14.2.0
nios2                     defconfig    gcc-15.1.0
parisc                    defconfig    gcc-15.1.0
parisc64                  defconfig    gcc-15.1.0
powerpc            ppc64e_defconfig    clang-21
powerpc           tqm8560_defconfig    clang-21
sh                      allnoconfig    gcc-15.1.0
sparc                   allnoconfig    gcc-15.1.0
sparc                     defconfig    gcc-15.1.0
x86_64                        kexec    clang-20
x86_64                     rhel-9.4    clang-20
xtensa                  allnoconfig    gcc-15.1.0
xtensa        cadence_csp_defconfig    clang-21

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

                 reply	other threads:[~2025-07-06 23:04 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=202507070757.U9X4Pn4I-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 NNTP newsgroup(s).