From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [Intel-wired-lan] [tnguy-next-queue:dev-queue] BUILD SUCCESS f1067cbc5aa228e858780fdffd6d72a0682be369
Date: Thu, 06 Oct 2022 19:12:17 +0800 [thread overview]
Message-ID: <633eb811.SCAUp32GenBkuKiV%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
branch HEAD: f1067cbc5aa228e858780fdffd6d72a0682be369 i40e: Fix flow-type by setting GL_HASH_INSET registers
elapsed time: 723m
configs tested: 96
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
um i386_defconfig
um x86_64_defconfig
arc defconfig
alpha defconfig
x86_64 defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
s390 defconfig
s390 allmodconfig
powerpc allnoconfig
mips allyesconfig
x86_64 rhel-8.3-syz
powerpc allmodconfig
m68k allmodconfig
arm defconfig
sh allmodconfig
arc allyesconfig
x86_64 rhel-8.3-func
s390 allyesconfig
riscv randconfig-r042-20221005
i386 defconfig
arc randconfig-r043-20221005
x86_64 rhel-8.3-kunit
s390 randconfig-r044-20221005
alpha allyesconfig
x86_64 rhel-8.3-kvm
x86_64 rhel-8.3-kselftests
i386 randconfig-a011-20221003
m68k allyesconfig
i386 randconfig-a012-20221003
x86_64 randconfig-a011-20221003
arm64 allyesconfig
x86_64 randconfig-a014-20221003
i386 randconfig-a013-20221003
x86_64 randconfig-a012-20221003
x86_64 randconfig-a013-20221003
arm allyesconfig
x86_64 randconfig-a015-20221003
x86_64 randconfig-a016-20221003
i386 randconfig-a015-20221003
i386 randconfig-a016-20221003
i386 randconfig-a014-20221003
i386 allyesconfig
ia64 allmodconfig
arm eseries_pxa_defconfig
mips cobalt_defconfig
openrisc defconfig
nios2 alldefconfig
csky allnoconfig
alpha allnoconfig
arc allnoconfig
riscv allnoconfig
powerpc taishan_defconfig
powerpc eiger_defconfig
loongarch alldefconfig
powerpc mpc85xx_cds_defconfig
parisc generic-64bit_defconfig
i386 randconfig-c001
mips randconfig-c004-20221002
arc tb10x_defconfig
um alldefconfig
mips bigsur_defconfig
mips bcm47xx_defconfig
arm simpad_defconfig
i386 debian-10.3-kvm
i386 debian-10.3-kunit
i386 debian-10.3-func
m68k q40_defconfig
mips decstation_64_defconfig
powerpc tqm8548_defconfig
riscv nommu_virt_defconfig
riscv rv32_defconfig
riscv nommu_k210_defconfig
i386 debian-10.3-kselftests
i386 debian-10.3
riscv randconfig-r042-20221003
arc randconfig-r043-20221003
arc randconfig-r043-20221002
s390 randconfig-r044-20221003
powerpc cm5200_defconfig
arm viper_defconfig
clang tested configs:
hexagon randconfig-r045-20221005
x86_64 randconfig-a003-20221003
x86_64 randconfig-a005-20221003
hexagon randconfig-r041-20221005
x86_64 randconfig-a002-20221003
i386 randconfig-a003-20221003
x86_64 randconfig-a001-20221003
i386 randconfig-a002-20221003
x86_64 randconfig-a004-20221003
i386 randconfig-a001-20221003
x86_64 randconfig-a006-20221003
i386 randconfig-a004-20221003
i386 randconfig-a005-20221003
i386 randconfig-a006-20221003
x86_64 randconfig-k001
--
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-10-06 11:12 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=633eb811.SCAUp32GenBkuKiV%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