All of 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:master] BUILD REGRESSION d82303df06481235fe7cbaf605075e0c2c87e99b
Date: Thu, 17 Nov 2022 19:18:55 +0800	[thread overview]
Message-ID: <6376189f.EufUiUPEOFrMVPwx%lkp@intel.com> (raw)

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git master
branch HEAD: d82303df06481235fe7cbaf605075e0c2c87e99b  mlxsw: update adjfine to use adjust_by_scaled_ppm

Error/Warning reports:

https://lore.kernel.org/oe-kbuild-all/202211151913.CCNjaoPq-lkp@intel.com

Error/Warning: (recently discovered and may have been fixed)

include/net/sock.h:387:37: error: 'const struct sock_common' has no member named 'skc_v6_rcv_saddr'; did you mean 'skc_rcv_saddr'?

Unverified Error/Warning (likely false positive, please contact us if interested):

net/core/dev.c:6409 napi_disable() error: uninitialized symbol 'new'.

Error/Warning ids grouped by kconfigs:

gcc_recent_errors
|-- alpha-defconfig
|   `-- include-net-sock.h:error:const-struct-sock_common-has-no-member-named-skc_v6_rcv_saddr
|-- arc-defconfig
|   `-- include-net-sock.h:error:const-struct-sock_common-has-no-member-named-skc_v6_rcv_saddr
`-- i386-randconfig-m021
    `-- net-core-dev.c-napi_disable()-error:uninitialized-symbol-new-.

elapsed time: 877m

configs tested: 34
configs skipped: 2

gcc tested configs:
arc                  randconfig-r043-20221117
riscv                randconfig-r042-20221117
s390                 randconfig-r044-20221117
alpha                               defconfig
arc                                 defconfig
s390                             allmodconfig
um                             i386_defconfig
um                           x86_64_defconfig
i386                                defconfig
s390                                defconfig
x86_64                          rhel-8.3-func
s390                             allyesconfig
x86_64                    rhel-8.3-kselftests
x86_64                           rhel-8.3-syz
x86_64                         rhel-8.3-kunit
x86_64                           rhel-8.3-kvm
m68k                             allmodconfig
arc                              allyesconfig
alpha                            allyesconfig
powerpc                          allmodconfig
m68k                             allyesconfig
mips                             allyesconfig
powerpc                           allnoconfig
sh                               allmodconfig
x86_64                              defconfig
arm                                 defconfig
i386                             allyesconfig
x86_64                               rhel-8.3
arm64                            allyesconfig
arm                              allyesconfig
x86_64                           allyesconfig

clang tested configs:
x86_64                        randconfig-a016
hexagon              randconfig-r041-20221117
hexagon              randconfig-r045-20221117

-- 
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-17 11:20 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=6376189f.EufUiUPEOFrMVPwx%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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.