From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: linux-next: build warnings after merge of the kbuild tree
Date: Wed, 17 Aug 2016 11:44:43 +1000 [thread overview]
Message-ID: <20160817114443.67675413@canb.auug.org.au> (raw)
Hi Michal,
After merging the kbuild tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:
WARNING: 25 bad relocations
c000000000cf2570 R_PPC64_ADDR64 __crc___arch_hweight16
c000000000cf2578 R_PPC64_ADDR64 __crc___arch_hweight32
c000000000cf2580 R_PPC64_ADDR64 __crc___arch_hweight64
c000000000cf2588 R_PPC64_ADDR64 __crc___arch_hweight8
c000000000cf2678 R_PPC64_ADDR64 __crc___bswapdi2
c000000000cf2690 R_PPC64_ADDR64 __crc___clear_user
c000000000cf26b8 R_PPC64_ADDR64 __crc___copy_tofrom_user
c000000000cf2728 R_PPC64_ADDR64 __crc___csum_partial
c000000000cf3f90 R_PPC64_ADDR64 __crc_copy_page
c000000000cf40e0 R_PPC64_ADDR64 __crc_csum_partial_copy_generic
c000000000cf4100 R_PPC64_ADDR64 __crc_current_stack_pointer
c000000000cf4928 R_PPC64_ADDR64 __crc_empty_zero_page
c000000000cf4db0 R_PPC64_ADDR64 __crc_flush_dcache_range
c000000000cf4dc0 R_PPC64_ADDR64 __crc_flush_icache_range
c000000000cf6470 R_PPC64_ADDR64 __crc_load_fp_state
c000000000cf6488 R_PPC64_ADDR64 __crc_load_vr_state
c000000000cf68d0 R_PPC64_ADDR64 __crc_memchr
c000000000cf68e0 R_PPC64_ADDR64 __crc_memcmp
c000000000cf68e8 R_PPC64_ADDR64 __crc_memcpy
c000000000cf6900 R_PPC64_ADDR64 __crc_memmove
c000000000cf6988 R_PPC64_ADDR64 __crc_memset
c000000000cf9328 R_PPC64_ADDR64 __crc_store_fp_state
c000000000cf9330 R_PPC64_ADDR64 __crc_store_vr_state
c000000000cf93d0 R_PPC64_ADDR64 __crc_strncmp
c000000000cf93d8 R_PPC64_ADDR64 __crc_strncpy
Introduced by commit
9445aa1a3062 ("ppc: move exports to definitions")
I have reverted that commit for today.
[cc-ing the ppc guys for clues - also involved is commit
22823ab419d8 ("EXPORT_SYMBOL() for asm")
]
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-08-17 1:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 1:44 Stephen Rothwell [this message]
2016-08-17 12:59 ` linux-next: build warnings after merge of the kbuild tree Michal Marek
2016-08-18 1:09 ` Nicholas Piggin
2016-08-19 3:38 ` Stephen Rothwell
2016-08-19 5:09 ` Stephen Rothwell
2016-08-19 5:32 ` Nicholas Piggin
2016-08-19 8:37 ` Michal Marek
2016-08-19 10:44 ` Nicholas Piggin
2016-08-22 10:47 ` Nicholas Piggin
2016-08-26 3:58 ` Nicholas Piggin
2016-08-26 6:21 ` Nicholas Mc Guire
2019-09-04 0:13 Stephen Rothwell
2019-09-04 1:00 ` Masahiro Yamada
2019-09-04 6:22 ` Masahiro Yamada
2019-09-04 12:33 ` Stephen Rothwell
2019-09-04 12:32 ` Stephen Rothwell
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=20160817114443.67675413@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=viro@zeniv.linux.org.uk \
/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).