From: kernel test robot <lkp@intel.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: [dtor-input:for-linus] BUILD SUCCESS 4f9786035f9e519db41375818e1d0b5f20da2f10
Date: Wed, 04 Jun 2025 11:27:55 +0800 [thread overview]
Message-ID: <202506041145.e1yytv4n-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
branch HEAD: 4f9786035f9e519db41375818e1d0b5f20da2f10 Merge branch 'next' into for-linus
elapsed time: 1455m
configs tested: 34
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc-15.1.0
arc allmodconfig gcc-15.1.0
arc allyesconfig gcc-15.1.0
arm allmodconfig gcc-15.1.0
arm allyesconfig gcc-15.1.0
arm64 allmodconfig clang-19
hexagon allmodconfig clang-17
hexagon allyesconfig clang-21
i386 allmodconfig gcc-12
i386 allnoconfig gcc-12
i386 allyesconfig gcc-12
i386 defconfig clang-20
loongarch allmodconfig gcc-15.1.0
m68k allmodconfig gcc-15.1.0
m68k allyesconfig gcc-15.1.0
microblaze allyesconfig gcc-15.1.0
openrisc allyesconfig gcc-15.1.0
parisc allmodconfig gcc-15.1.0
parisc allyesconfig gcc-15.1.0
powerpc allmodconfig gcc-15.1.0
powerpc allyesconfig clang-21
riscv allmodconfig clang-21
riscv allyesconfig clang-16
s390 allmodconfig clang-18
s390 allyesconfig gcc-15.1.0
sh allmodconfig gcc-15.1.0
sh allyesconfig gcc-15.1.0
sparc allmodconfig gcc-15.1.0
um allmodconfig clang-19
um allyesconfig gcc-12
x86_64 allnoconfig clang-20
x86_64 allyesconfig clang-20
x86_64 defconfig gcc-11
x86_64 rhel-9.4-rust clang-18
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-06-04 3:28 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=202506041145.e1yytv4n-lkp@intel.com \
--to=lkp@intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.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;
as well as URLs for NNTP newsgroup(s).