public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel•com>
To: Russell King <rmk+kernel@armlinux•org.uk>
Cc: kbuild-all@lists•01.org, linux-arm-kernel@lists•infradead.org
Subject: [arm:zii 11/35] ERROR: "phy_sfp_probe" [drivers/net/phy/marvell10g.ko] undefined!
Date: Sat, 19 Oct 2019 02:33:41 +0800	[thread overview]
Message-ID: <201910190238.oS2ASagx%lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 822 bytes --]

tree:   git://git.armlinux.org.uk/~rmk/linux-arm.git zii
head:   5950d2005083b57da3a132f1147e1c55d8d23826
commit: 16eea53cb10b07a44e39c8d3d76c14261eb3cc4a [11/35] net: phy: marvell10g: add SFP+ support
config: x86_64-randconfig-d001-201941 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-13) 7.4.0
reproduce:
        git checkout 16eea53cb10b07a44e39c8d3d76c14261eb3cc4a
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel•com>

All errors (new ones prefixed by >>):

>> ERROR: "phy_sfp_probe" [drivers/net/phy/marvell10g.ko] undefined!

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31370 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

                 reply	other threads:[~2019-10-18 18:34 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=201910190238.oS2ASagx%lkp@intel.com \
    --to=lkp@intel$(echo .)com \
    --cc=kbuild-all@lists$(echo .)01.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=rmk+kernel@armlinux$(echo .)org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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