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 a3f37717b0b479dffa856f737bc067df359b0684
Date: Thu, 30 Jun 2022 12:49:00 +0800 [thread overview]
Message-ID: <62bd2b3c.TcStPMh8uLZKcvWb%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
branch HEAD: a3f37717b0b479dffa856f737bc067df359b0684 ping: fix ipv6 ping socket flow labels
elapsed time: 728m
configs tested: 46
configs skipped: 2
The following configs have been built successfully.
More configs may be tested in the coming days.
gcc tested configs:
powerpc allnoconfig
mips allyesconfig
powerpc allmodconfig
sh allmodconfig
i386 defconfig
i386 allyesconfig
arc allyesconfig
alpha allyesconfig
m68k allmodconfig
m68k allyesconfig
i386 randconfig-a001
i386 randconfig-a003
i386 randconfig-a005
x86_64 randconfig-a015
x86_64 randconfig-a013
x86_64 randconfig-a011
i386 randconfig-a012
i386 randconfig-a014
x86_64 randconfig-a004
x86_64 randconfig-a002
x86_64 randconfig-a006
arc randconfig-r043-20220629
s390 randconfig-r044-20220629
riscv randconfig-r042-20220629
um x86_64_defconfig
um i386_defconfig
x86_64 allyesconfig
x86_64 defconfig
x86_64 rhel-8.3
x86_64 rhel-8.3-kselftests
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-syz
clang tested configs:
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
x86_64 randconfig-a014
x86_64 randconfig-a016
x86_64 randconfig-a012
i386 randconfig-a013
i386 randconfig-a011
x86_64 randconfig-a005
x86_64 randconfig-a001
x86_64 randconfig-a003
hexagon randconfig-r045-20220629
hexagon randconfig-r041-20220629
--
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-06-30 4:49 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=62bd2b3c.TcStPMh8uLZKcvWb%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