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 f2bb566f5c977ff010baaa9e5e14d9a75b06e5f2
Date: Wed, 30 Nov 2022 21:51:04 +0800 [thread overview]
Message-ID: <63875fc8.x1ImFMBKcqeCY4M0%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git master
branch HEAD: f2bb566f5c977ff010baaa9e5e14d9a75b06e5f2 Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
elapsed time: 738m
configs tested: 99
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
s390 defconfig
s390 allmodconfig
arc defconfig
alpha defconfig
s390 allyesconfig
um x86_64_defconfig
um i386_defconfig
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-syz
x86_64 rhel-8.3-kunit
x86_64 allnoconfig
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kselftests
sh sh7763rdp_defconfig
powerpc ps3_defconfig
xtensa cadence_csp_defconfig
mips maltasmvp_defconfig
ia64 allmodconfig
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
arm64 allyesconfig
arm defconfig
arm allyesconfig
i386 randconfig-a001-20221128
i386 randconfig-a005-20221128
i386 randconfig-a006-20221128
i386 randconfig-a004-20221128
i386 randconfig-a003-20221128
i386 randconfig-a002-20221128
i386 allyesconfig
i386 defconfig
m68k allyesconfig
m68k allmodconfig
arc allyesconfig
alpha allyesconfig
powerpc allnoconfig
i386 randconfig-c001
x86_64 randconfig-a002-20221128
x86_64 randconfig-a001-20221128
x86_64 randconfig-a004-20221128
x86_64 randconfig-a006-20221128
x86_64 randconfig-a005-20221128
x86_64 randconfig-a003-20221128
sh allmodconfig
mips allyesconfig
powerpc allmodconfig
arm omap2plus_defconfig
sh j2_defconfig
mips ci20_defconfig
sh sdk7786_defconfig
arc haps_hs_smp_defconfig
powerpc cm5200_defconfig
arm lpd270_defconfig
x86_64 randconfig-a011
x86_64 randconfig-a013
x86_64 randconfig-a015
x86_64 randconfig-a006
x86_64 randconfig-a004
x86_64 randconfig-a002
csky defconfig
nios2 defconfig
mips gcw0_defconfig
xtensa xip_kc705_defconfig
arm oxnas_v6_defconfig
sh lboxre2_defconfig
sh se7750_defconfig
sh espt_defconfig
sparc64 alldefconfig
powerpc currituck_defconfig
arc allnoconfig
loongarch defconfig
loongarch allnoconfig
loongarch allmodconfig
clang tested configs:
x86_64 randconfig-a012
x86_64 randconfig-a014
x86_64 randconfig-a016
s390 randconfig-r044-20221128
hexagon randconfig-r041-20221128
riscv randconfig-r042-20221128
hexagon randconfig-r045-20221128
i386 randconfig-a014-20221128
i386 randconfig-a011-20221128
i386 randconfig-a013-20221128
i386 randconfig-a016-20221128
i386 randconfig-a012-20221128
i386 randconfig-a015-20221128
x86_64 randconfig-k001-20221128
i386 randconfig-a002
i386 randconfig-a006
i386 randconfig-a004
x86_64 randconfig-a011-20221128
x86_64 randconfig-a014-20221128
x86_64 randconfig-a012-20221128
x86_64 randconfig-a013-20221128
x86_64 randconfig-a016-20221128
x86_64 randconfig-a015-20221128
arm tct_hammer_defconfig
arm vexpress_defconfig
--
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-11-30 13:51 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=63875fc8.x1ImFMBKcqeCY4M0%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