From: kernel test robot <lkp@intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: [tytso-ext4:dev] BUILD SUCCESS 97e211ad1a34a5a979558a037619b9e633ca8620
Date: Sat, 25 Jul 2026 19:30:38 +0800 [thread overview]
Message-ID: <202607251927.joRS6fR1-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
branch HEAD: 97e211ad1a34a5a979558a037619b9e633ca8620 jbd2: align h_type and h_line_no in the handle structure on byte boundaries
elapsed time: 1271m
configs tested: 68
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allnoconfig gcc-16.1.0
alpha allyesconfig gcc-16.1.0
alpha defconfig gcc-16.1.0
arc allmodconfig gcc-16.1.0
arc allyesconfig gcc-16.1.0
arc randconfig-001-20260725 gcc-11.5.0
arc randconfig-002-20260725 gcc-8.5.0
arm randconfig-001-20260725 gcc-8.5.0
arm randconfig-002-20260725 clang-21
arm randconfig-003-20260725 gcc-10.5.0
arm randconfig-004-20260725 gcc-15.2.0
csky allmodconfig gcc-16.1.0
csky randconfig-001-20260725 gcc-9.5.0
csky randconfig-002-20260725 gcc-16.1.0
hexagon randconfig-001-20260725 clang-17
hexagon randconfig-002-20260725 clang-24
i386 allmodconfig gcc-14
i386 buildonly-randconfig-001 gcc-14
i386 buildonly-randconfig-001-20260725 clang-22
i386 buildonly-randconfig-002-20260725 gcc-14
i386 buildonly-randconfig-003-20260725 clang-22
i386 buildonly-randconfig-004-20260725 clang-22
i386 buildonly-randconfig-005-20260725 gcc-14
i386 buildonly-randconfig-006-20260725 gcc-14
i386 randconfig-001-20260725 clang-22
i386 randconfig-002-20260725 gcc-14
i386 randconfig-003-20260725 gcc-14
i386 randconfig-004-20260725 gcc-12
i386 randconfig-005-20260725 clang-22
i386 randconfig-006-20260725 gcc-14
i386 randconfig-007-20260725 gcc-14
loongarch defconfig clang-24
loongarch randconfig-001-20260725 gcc-16.1.0
loongarch randconfig-002-20260725 gcc-13.4.0
nios2 allmodconfig gcc-11.5.0
nios2 allnoconfig gcc-11.5.0
nios2 randconfig-001-20260725 gcc-11.5.0
nios2 randconfig-002-20260725 gcc-9.5.0
parisc allmodconfig gcc-16.1.0
parisc allyesconfig gcc-16.1.0
parisc defconfig gcc-16.1.0
parisc randconfig-001 gcc-8.5.0
parisc randconfig-001-20260725 gcc-10.5.0
parisc randconfig-002-20260725 gcc-12.5.0
powerpc mpc5200_defconfig clang-24
powerpc randconfig-001-20260725 gcc-9.5.0
powerpc randconfig-002-20260725 gcc-15.2.0
powerpc64 randconfig-001-20260725 clang-17
powerpc64 randconfig-002-20260725 clang-24
riscv randconfig-001 gcc-13.4.0
riscv randconfig-001-20260725 gcc-8.5.0
riscv randconfig-002-20260725 gcc-8.5.0
s390 randconfig-001-20260725 gcc-10.5.0
s390 randconfig-002-20260725 gcc-16.1.0
sh defconfig gcc-16.1.0
sh randconfig-001-20260725 gcc-16.1.0
sh randconfig-002-20260725 gcc-11.5.0
sparc randconfig-001-20260725 gcc-16.1.0
sparc randconfig-002-20260725 gcc-8.5.0
sparc64 randconfig-001-20260725 gcc-8.5.0
sparc64 randconfig-002-20260725 gcc-10.5.0
um randconfig-001-20260725 gcc-14
x86_64 randconfig-071-20260725 gcc-14
x86_64 randconfig-072-20260725 gcc-14
x86_64 randconfig-073-20260725 gcc-14
x86_64 randconfig-074-20260725 gcc-14
x86_64 randconfig-075-20260725 gcc-14
x86_64 randconfig-076-20260725 clang-22
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-25 11:31 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=202607251927.joRS6fR1-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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