From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [Intel-wired-lan] [tnguy-next-queue:master] BUILD SUCCESS 1f17708b47a99ca5bcad594a6f8d14cb016edfd2
Date: Wed, 20 Jul 2022 19:24:52 +0800 [thread overview]
Message-ID: <62d7e604.yJC5XD7TICz29xF+%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git master
branch HEAD: 1f17708b47a99ca5bcad594a6f8d14cb016edfd2 sfc: update MCDI protocol headers
elapsed time: 802m
configs tested: 97
configs skipped: 3
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
arm64 allyesconfig
arm defconfig
arm allyesconfig
i386 randconfig-c001
arm realview_defconfig
arm rpc_defconfig
powerpc sequoia_defconfig
powerpc mpc837x_rdb_defconfig
powerpc sam440ep_defconfig
xtensa smp_lx200_defconfig
arm pxa3xx_defconfig
powerpc maple_defconfig
m68k m5307c3_defconfig
powerpc ep88xc_defconfig
arm footbridge_defconfig
x86_64 defconfig
sh sh7757lcr_defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv nommu_k210_defconfig
riscv allnoconfig
i386 debian-10.3-kselftests
i386 debian-10.3
loongarch defconfig
loongarch allnoconfig
csky allnoconfig
alpha allnoconfig
arc allnoconfig
m68k allyesconfig
m68k allmodconfig
arc allyesconfig
alpha allyesconfig
powerpc allnoconfig
mips allyesconfig
powerpc allmodconfig
sh allmodconfig
i386 allyesconfig
i386 defconfig
x86_64 randconfig-a006
x86_64 randconfig-a002
x86_64 randconfig-a004
x86_64 randconfig-a014-20220718
x86_64 randconfig-a016-20220718
x86_64 randconfig-a012-20220718
x86_64 randconfig-a013-20220718
x86_64 randconfig-a015-20220718
x86_64 randconfig-a011-20220718
i386 randconfig-a015-20220718
i386 randconfig-a011-20220718
i386 randconfig-a012-20220718
i386 randconfig-a014-20220718
i386 randconfig-a016-20220718
i386 randconfig-a013-20220718
i386 randconfig-a012
i386 randconfig-a014
i386 randconfig-a016
s390 randconfig-r044-20220718
riscv randconfig-r042-20220718
arc randconfig-r043-20220718
x86_64 rhel-8.3-kselftests
um x86_64_defconfig
um i386_defconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
x86_64 allyesconfig
x86_64 rhel-8.3
clang tested configs:
arm am200epdkit_defconfig
riscv alldefconfig
arm magician_defconfig
mips malta_defconfig
hexagon alldefconfig
mips ath25_defconfig
x86_64 randconfig-k001
x86_64 randconfig-a005
x86_64 randconfig-a003
x86_64 randconfig-a001
i386 randconfig-a002
i386 randconfig-a006
i386 randconfig-a004
i386 randconfig-a004-20220718
i386 randconfig-a001-20220718
i386 randconfig-a005-20220718
i386 randconfig-a002-20220718
i386 randconfig-a006-20220718
i386 randconfig-a003-20220718
x86_64 randconfig-a001-20220718
x86_64 randconfig-a005-20220718
x86_64 randconfig-a003-20220718
x86_64 randconfig-a002-20220718
x86_64 randconfig-a006-20220718
x86_64 randconfig-a004-20220718
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
hexagon randconfig-r041-20220718
hexagon randconfig-r045-20220718
--
0-DAY CI Kernel Test Service
https://01.org/lkp
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
reply other threads:[~2022-07-20 11:25 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=62d7e604.yJC5XD7TICz29xF+%lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-wired-lan@lists.osuosl.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