Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, robh+dt@kernel.org, mark.rutland@arm.com,
	matthias.bgg@gmail.com, kishon@ti.com, james.hogan@imgtec.com,
	John Crispin <john@phrozen.org>,
	Harvey Hunt <harvey.hunt@imgtec.com>,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [V6 1/2] phy: ralink-usb: add driver for Mediatek/Ralink
Date: Fri, 18 Aug 2017 02:10:28 +0800	[thread overview]
Message-ID: <201708180207.QOaO7OFk%fengguang.wu@intel.com> (raw)
In-Reply-To: <1502801223-20833-1-git-send-email-harvey.hunt@imgtec.com>

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

Hi John,

[auto build test ERROR on phy/next]
[also build test ERROR on v4.13-rc5 next-20170817]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Harvey-Hunt/phy-ralink-usb-add-driver-for-Mediatek-Ralink/20170817-212130
base:   https://git.kernel.org/pub/scm/linux/kernel/git/kishon/linux-phy.git next
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=mips 

All errors (new ones prefixed by >>):

   drivers/phy/phy-ralink-usb.o: In function `ralink_usb_phy_power_off':
>> phy-ralink-usb.c:(.text+0x1c): undefined reference to `rt_sysc_membase'
   phy-ralink-usb.c:(.text+0x24): undefined reference to `rt_sysc_membase'
   drivers/phy/phy-ralink-usb.o: In function `ralink_usb_phy_power_on':
   phy-ralink-usb.c:(.text+0x84): undefined reference to `rt_sysc_membase'
   phy-ralink-usb.c:(.text+0x8c): undefined reference to `rt_sysc_membase'
   phy-ralink-usb.c:(.text+0xdc): undefined reference to `rt_sysc_membase'
   drivers/phy/phy-ralink-usb.o:phy-ralink-usb.c:(.text+0x1c4): more undefined references to `rt_sysc_membase' follow

---
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: 47306 bytes --]

      parent reply	other threads:[~2017-08-17 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 12:47 [V6 1/2] phy: ralink-usb: add driver for Mediatek/Ralink Harvey Hunt
     [not found] ` <1502801223-20833-1-git-send-email-harvey.hunt-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
2017-08-15 12:47   ` [V6 2/2] dt-bindings: phy: Add bindings for ralink-usb PHY Harvey Hunt
2017-08-16 13:57   ` [V6 1/2] phy: ralink-usb: add driver for Mediatek/Ralink Kishon Vijay Abraham I
2017-08-16 16:02     ` Harvey Hunt
2017-08-17 18:10 ` kbuild test robot [this message]

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=201708180207.QOaO7OFk%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=harvey.hunt@imgtec.com \
    --cc=james.hogan@imgtec.com \
    --cc=john@phrozen.org \
    --cc=kbuild-all@01.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.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