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-next-queue:dev-queue] BUILD SUCCESS 189a79207ab4e0e7e5566551bdad49fae944bb1a
Date: Wed, 14 Sep 2022 21:22:20 +0800	[thread overview]
Message-ID: <6321d58c.VpYf6BlodGagyEU+%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
branch HEAD: 189a79207ab4e0e7e5566551bdad49fae944bb1a  i40e: Add appropriate error message logged for incorrect duplex setting

elapsed time: 727m

configs tested: 58
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
i386                                defconfig
i386                 randconfig-a001-20220912
i386                 randconfig-a002-20220912
i386                 randconfig-a003-20220912
powerpc                           allnoconfig
x86_64                    rhel-8.3-kselftests
x86_64                          rhel-8.3-func
arm                                 defconfig
x86_64                         rhel-8.3-kunit
i386                 randconfig-a005-20220912
x86_64                           rhel-8.3-kvm
i386                 randconfig-a004-20220912
x86_64                           rhel-8.3-syz
i386                 randconfig-a006-20220912
x86_64               randconfig-a001-20220912
x86_64               randconfig-a002-20220912
x86_64               randconfig-a003-20220912
m68k                             allmodconfig
x86_64                              defconfig
arm64                            allyesconfig
x86_64               randconfig-a004-20220912
riscv                randconfig-r042-20220911
i386                             allyesconfig
arm                              allyesconfig
x86_64                           allyesconfig
x86_64               randconfig-a005-20220912
arc                  randconfig-r043-20220912
x86_64               randconfig-a006-20220912
x86_64                               rhel-8.3
arc                              allyesconfig
arc                  randconfig-r043-20220911
sh                               allmodconfig
s390                 randconfig-r044-20220911
mips                             allyesconfig
powerpc                          allmodconfig
m68k                             allyesconfig
alpha                            allyesconfig
ia64                             allmodconfig

clang tested configs:
x86_64               randconfig-a011-20220912
i386                 randconfig-a013-20220912
x86_64               randconfig-a012-20220912
hexagon              randconfig-r041-20220912
i386                 randconfig-a011-20220912
x86_64               randconfig-a013-20220912
hexagon              randconfig-r045-20220911
i386                 randconfig-a012-20220912
x86_64               randconfig-a014-20220912
i386                 randconfig-a014-20220912
x86_64               randconfig-a016-20220912
hexagon              randconfig-r041-20220911
i386                 randconfig-a015-20220912
hexagon              randconfig-r045-20220912
x86_64               randconfig-a015-20220912
s390                 randconfig-r044-20220912
riscv                randconfig-r042-20220912
i386                 randconfig-a016-20220912

-- 
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-09-14 13:23 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=6321d58c.VpYf6BlodGagyEU+%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