From: Al Viro <viro@ZenIV.linux.org.uk>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, linux-kbuild@vger.kernel.org,
Michal Marek <mmarek@suse.com>
Subject: Re: [vfs:asm-exports 6/6] ERROR: "__raw_readsb" [drivers/ata/pata_pcmcia.ko] undefined!
Date: Thu, 14 Jan 2016 04:33:14 +0000 [thread overview]
Message-ID: <20160114043314.GV17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <201601141009.4c7T6SyL%fengguang.wu@intel.com>
On Thu, Jan 14, 2016 at 10:50:12AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git asm-exports
> head: 5719a6be97e89c65e2b432b45850100c96c7419a
> commit: 5719a6be97e89c65e2b432b45850100c96c7419a [6/6] arm: move exports to definitions
> config: arm-viper_defconfig (attached as .config)
> 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 5719a6be97e89c65e2b432b45850100c96c7419a
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "__raw_readsb" [drivers/ata/pata_pcmcia.ko] undefined!
> >> ERROR: "__raw_writesb" [drivers/ata/pata_pcmcia.ko] undefined!
Arrgh... OK, I see what's going on - export in a lib-y object. For lib/*.c
we deal with that by putting such objects into obj-y; the same certainly
can be done for *.S, but I wonder if a better solution would be to have
lib-y objects scanned for __ksymtab_strings section (grepping in objdump -h
output) and treat the ones that have such as obj-y.
Comments?
parent reply other threads:[~2016-01-14 4:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <201601141009.4c7T6SyL%fengguang.wu@intel.com>]
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=20160114043314.GV17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.com \
/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).