From: kernel test robot <lkp@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: [linusw-pinctrl:for-next] BUILD SUCCESS cef56291a5de3e835813af1e74f422a11989e3d4
Date: Sun, 09 Jun 2024 05:46:10 +0800 [thread overview]
Message-ID: <202406090508.vFuetLpn-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git for-next
branch HEAD: cef56291a5de3e835813af1e74f422a11989e3d4 Merge branch 'devel' into for-next
elapsed time: 1449m
configs tested: 20
configs skipped: 1
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
openrisc allnoconfig gcc
openrisc defconfig gcc
parisc allnoconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allnoconfig gcc
riscv allnoconfig gcc
riscv defconfig clang
s390 allnoconfig clang
s390 defconfig clang
sh allnoconfig gcc
sh defconfig gcc
sparc allnoconfig gcc
sparc defconfig gcc
sparc64 defconfig gcc
um allnoconfig clang
um defconfig clang
um i386_defconfig gcc
um x86_64_defconfig clang
xtensa allnoconfig gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-06-08 21:46 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=202406090508.vFuetLpn-lkp@intel.com \
--to=lkp@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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).