From: kernel test robot <lkp@intel.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: linux-gpio@vger.kernel.org
Subject: [brgl:gpio/for-next] BUILD SUCCESS b0ce9ce408b6cfbce6c720c7eb084e6d81a04434
Date: Sat, 10 Jun 2023 14:55:09 +0800 [thread overview]
Message-ID: <202306101407.1tFFCxQC-lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/brgl/linux.git gpio/for-next
branch HEAD: b0ce9ce408b6cfbce6c720c7eb084e6d81a04434 gpiolib: Do not unexport GPIO on freeing
elapsed time: 846m
configs tested: 91
configs skipped: 4
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-r012-20230608 gcc
alpha randconfig-r025-20230608 gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-r033-20230608 gcc
arm allmodconfig gcc
arm allyesconfig gcc
arm defconfig gcc
arm moxart_defconfig clang
arm pxa168_defconfig clang
arm64 allyesconfig gcc
arm64 defconfig gcc
csky defconfig gcc
hexagon randconfig-r013-20230608 clang
hexagon randconfig-r023-20230608 clang
i386 alldefconfig gcc
i386 allyesconfig gcc
i386 debian-10.3 gcc
i386 defconfig gcc
i386 randconfig-i051-20230608 gcc
i386 randconfig-i052-20230608 gcc
i386 randconfig-i053-20230608 gcc
i386 randconfig-i054-20230608 gcc
i386 randconfig-i055-20230608 gcc
i386 randconfig-i056-20230608 gcc
loongarch allmodconfig gcc
loongarch allnoconfig gcc
loongarch defconfig gcc
m68k allmodconfig gcc
m68k allyesconfig gcc
m68k defconfig gcc
microblaze randconfig-r034-20230608 gcc
mips allmodconfig gcc
mips allyesconfig gcc
mips bmips_stb_defconfig clang
mips gpr_defconfig gcc
nios2 defconfig gcc
openrisc randconfig-r021-20230608 gcc
openrisc randconfig-r022-20230608 gcc
parisc allyesconfig gcc
parisc defconfig gcc
parisc64 defconfig gcc
powerpc allmodconfig gcc
powerpc allnoconfig gcc
powerpc lite5200b_defconfig clang
powerpc skiroot_defconfig clang
powerpc tqm8560_defconfig clang
riscv alldefconfig clang
riscv allmodconfig gcc
riscv allnoconfig gcc
riscv allyesconfig gcc
riscv defconfig gcc
riscv randconfig-r015-20230608 clang
riscv randconfig-r032-20230608 gcc
riscv randconfig-r036-20230608 gcc
riscv rv32_defconfig gcc
s390 allmodconfig gcc
s390 allyesconfig gcc
s390 debug_defconfig gcc
s390 defconfig gcc
s390 randconfig-r014-20230608 clang
s390 randconfig-r026-20230608 clang
sh allmodconfig gcc
sh ap325rxa_defconfig gcc
sh edosk7705_defconfig gcc
sparc allyesconfig gcc
sparc defconfig gcc
sparc randconfig-r024-20230608 gcc
sparc randconfig-r031-20230608 gcc
sparc randconfig-r035-20230608 gcc
um i386_defconfig gcc
um x86_64_defconfig clang
um x86_64_defconfig gcc
x86_64 allyesconfig gcc
x86_64 defconfig gcc
x86_64 kexec gcc
x86_64 randconfig-a001-20230608 gcc
x86_64 randconfig-a002-20230608 gcc
x86_64 randconfig-a003-20230608 gcc
x86_64 randconfig-a004-20230608 gcc
x86_64 randconfig-a005-20230608 gcc
x86_64 randconfig-a006-20230608 gcc
x86_64 randconfig-a011-20230608 clang
x86_64 randconfig-a012-20230608 clang
x86_64 randconfig-a013-20230608 clang
x86_64 randconfig-a014-20230608 clang
x86_64 randconfig-a015-20230608 clang
x86_64 randconfig-a016-20230608 clang
x86_64 rhel-8.3-rust clang
x86_64 rhel-8.3 gcc
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-06-10 6:55 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=202306101407.1tFFCxQC-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).