From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: [brgl:gpio/for-current] BUILD SUCCESS 976d3c6778e99390c6d854d140b746d12ea18a51
Date: Fri, 12 May 2023 12:39:02 +0800 [thread overview]
Message-ID: <20230512043902.9n4hk%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-current
branch HEAD: 976d3c6778e99390c6d854d140b746d12ea18a51 selftests: gpio: gpio-sim: Fix BUG: test FAILED due to recent change
elapsed time: 732m
configs tested: 90
configs skipped: 7
The following configs have been built successfully.
More configs may be tested in the coming days.
tested configs:
alpha allyesconfig gcc
alpha defconfig gcc
alpha randconfig-r015-20230509 gcc
alpha randconfig-r016-20230509 gcc
arc allyesconfig gcc
arc defconfig gcc
arc nsimosci_hs_smp_defconfig gcc
arc randconfig-r015-20230509 gcc
arc randconfig-r043-20230509 gcc
arc randconfig-r043-20230511 gcc
arc tb10x_defconfig gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm nhk8815_defconfig gcc
arm qcom_defconfig gcc
arm randconfig-r046-20230509 gcc
arm sunxi_defconfig gcc
arm64 allyesconfig gcc
arm64 defconfig gcc
arm64 randconfig-r013-20230509 clang
csky defconfig gcc
csky randconfig-r011-20230509 gcc
csky randconfig-r021-20230511 gcc
csky randconfig-r026-20230511 gcc
hexagon randconfig-r016-20230511 clang
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-a012 gcc
i386 randconfig-a014 gcc
i386 randconfig-a016 gcc
ia64 allmodconfig gcc
ia64 defconfig gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
m68k allmodconfig gcc
m68k defconfig gcc
m68k randconfig-r011-20230509 gcc
microblaze randconfig-r012-20230511 gcc
mips allmodconfig gcc
mips allyesconfig gcc
mips randconfig-r016-20230509 gcc
nios2 defconfig gcc
nios2 randconfig-r012-20230509 gcc
nios2 randconfig-r016-20230511 gcc
openrisc randconfig-r013-20230511 gcc
parisc defconfig gcc
parisc randconfig-r013-20230511 gcc
parisc randconfig-r024-20230511 gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc randconfig-r001-20230511 clang
powerpc randconfig-r015-20230511 gcc
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv defconfig gcc
riscv randconfig-r004-20230511 clang
riscv randconfig-r006-20230511 clang
riscv randconfig-r042-20230511 gcc
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 defconfig gcc
s390 randconfig-r014-20230509 clang
s390 randconfig-r014-20230511 gcc
s390 randconfig-r022-20230511 gcc
s390 randconfig-r044-20230511 gcc
sh allmodconfig gcc
sh randconfig-r011-20230511 gcc
sh se7712_defconfig gcc
sparc defconfig gcc
sparc randconfig-r015-20230511 gcc
um i386_defconfig gcc
um x86_64_defconfig gcc
x86_64 allnoconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 rhel-8.3-bpf gcc
x86_64 rhel-8.3-func gcc
x86_64 rhel-8.3-kselftests gcc
x86_64 rhel-8.3-kunit gcc
x86_64 rhel-8.3-kvm gcc
x86_64 rhel-8.3-ltp gcc
x86_64 rhel-8.3-syz gcc
x86_64 rhel-8.3 gcc
xtensa randconfig-r012-20230511 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-05-12 4: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=20230512043902.9n4hk%lkp@intel.com \
--to=lkp@intel.com \
--cc=bartosz.golaszewski@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).