mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: undefined reference to `physical_memsize'
Date: Sun, 29 Jan 2017 18:45:39 +0800	[thread overview]
Message-ID: <201701291836.pps9ArTU%fengguang.wu@intel.com> (raw)

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

Hi Hauke,

It's probably a bug fix that unveils the link errors.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   53cd1ad1a68fd10f677445e04ed63aa9ce39b36b
commit: a2724663494f7313f53da10d8c0a729c5e3c4dea mtd: nand: xway: fix build because of module functions
date:   4 weeks ago
config: mips-xway_defconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
        wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout a2724663494f7313f53da10d8c0a729c5e3c4dea
        # save the attached .config to linux build tree
        make.cross ARCH=mips 

All errors (new ones prefixed by >>):

   arch/mips/built-in.o: In function `vpe_run':
>> (.text+0x14990): undefined reference to `physical_memsize'
   arch/mips/built-in.o: In function `vpe_run':
   (.text+0x14994): undefined reference to `physical_memsize'

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

                 reply	other threads:[~2017-01-29 11:11 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=201701291836.pps9ArTU%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=hauke@hauke-m.de \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®