Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Intel Wired LAN <intel-wired-lan@lists.osuosl.org>
Subject: [Intel-wired-lan] [tnguy-net-queue:dev-queue] BUILD SUCCESS d8269c60b34315abfb87692172a769e48f3cef75
Date: Fri, 06 Jan 2023 16:48:18 +0800	[thread overview]
Message-ID: <63b7e052.Uui4a6k/k5AAciAx%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git dev-queue
branch HEAD: d8269c60b34315abfb87692172a769e48f3cef75  ice: fix out-of-bounds KASAN warning in virtchnl

elapsed time: 849m

configs tested: 62
configs skipped: 2

The following configs have been built successfully.
More configs may be tested in the coming days.

gcc tested configs:
powerpc                           allnoconfig
ia64                             allmodconfig
x86_64                            allnoconfig
sh                               allmodconfig
um                             i386_defconfig
um                           x86_64_defconfig
powerpc                          allmodconfig
mips                             allyesconfig
x86_64                           rhel-8.3-kvm
x86_64                           rhel-8.3-syz
arc                  randconfig-r043-20230105
x86_64                           rhel-8.3-bpf
x86_64                         rhel-8.3-kunit
s390                 randconfig-r044-20230105
arc                                 defconfig
s390                             allmodconfig
alpha                               defconfig
i386                          randconfig-a003
i386                          randconfig-a001
x86_64                              defconfig
alpha                            allyesconfig
s390                                defconfig
i386                          randconfig-a014
riscv                randconfig-r042-20230105
m68k                             allyesconfig
i386                          randconfig-a012
arc                              allyesconfig
x86_64                               rhel-8.3
x86_64                        randconfig-a004
i386                          randconfig-a005
s390                             allyesconfig
i386                          randconfig-a016
x86_64                          rhel-8.3-func
x86_64                        randconfig-a013
x86_64                           allyesconfig
x86_64                        randconfig-a002
x86_64                    rhel-8.3-kselftests
x86_64                        randconfig-a011
x86_64                        randconfig-a006
x86_64                        randconfig-a015
arm                                 defconfig
i386                                defconfig
arm64                            allyesconfig
arm                              allyesconfig
i386                             allyesconfig
m68k                             allmodconfig

clang tested configs:
arm                  randconfig-r046-20230105
hexagon              randconfig-r041-20230105
hexagon              randconfig-r045-20230105
i386                          randconfig-a002
i386                          randconfig-a004
i386                          randconfig-a013
i386                          randconfig-a011
x86_64                        randconfig-a014
i386                          randconfig-a006
i386                          randconfig-a015
x86_64                        randconfig-a001
x86_64                        randconfig-a016
x86_64                          rhel-8.3-rust
x86_64                        randconfig-a012
x86_64                        randconfig-a003
x86_64                        randconfig-a005

-- 
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:[~2023-01-06  8: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=63b7e052.Uui4a6k/k5AAciAx%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