linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-fsdevel@vger.kernel.org
Subject: Re: [vfs:work.asm-exports 8/12] (___ksymtab+clear_pages+0x0): undefined reference to `clear_pages'
Date: Tue, 9 Aug 2016 15:11:43 +0100	[thread overview]
Message-ID: <20160809141142.GP2356@ZenIV.linux.org.uk> (raw)
In-Reply-To: <201608091644.OyERZJJt%fengguang.wu@intel.com>

On Tue, Aug 09, 2016 at 04:55:46PM +0800, kbuild test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.asm-exports
> head:   e007c53397acb5554e226693e3bff54a312ccd96
> commit: 9445aa1a3062a75a4d9de78026816ebc941e7b99 [8/12] ppc: move exports to definitions
> config: powerpc-socrates_defconfig (attached as .config)
> compiler: powerpc-linux-gnu-gcc (Debian 5.4.0-6) 5.4.0 20160609
> 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 9445aa1a3062a75a4d9de78026816ebc941e7b99
>         # save the attached .config to linux build tree
>         make.cross ARCH=powerpc 
> 
> All errors (new ones prefixed by >>):
> 
>    arch/powerpc/kernel/built-in.o: In function `__ksymtab_clear_pages':
> >> (___ksymtab+clear_pages+0x0): undefined reference to `clear_pages'

Hadn't spotted the removal of clear_pages() definition when porting that
one.  Fixed and force-pushed.

      reply	other threads:[~2016-08-09 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09  8:55 [vfs:work.asm-exports 8/12] (___ksymtab+clear_pages+0x0): undefined reference to `clear_pages' kbuild test robot
2016-08-09 14:11 ` Al Viro [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=20160809141142.GP2356@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=fengguang.wu@intel.com \
    --cc=kbuild-all@01.org \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).