From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752340AbcHQNAG (ORCPT ); Wed, 17 Aug 2016 09:00:06 -0400 Received: from mx2.suse.de ([195.135.220.15]:36921 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750839AbcHQNAE (ORCPT ); Wed, 17 Aug 2016 09:00:04 -0400 Subject: Re: linux-next: build warnings after merge of the kbuild tree To: Stephen Rothwell References: <20160817114443.67675413@canb.auug.org.au> Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Al Viro , Michael Ellerman , Benjamin Herrenschmidt , PowerPC From: Michal Marek Message-ID: Date: Wed, 17 Aug 2016 14:59:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2 MIME-Version: 1.0 In-Reply-To: <20160817114443.67675413@canb.auug.org.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2016-08-17 03:44, Stephen Rothwell wrote: > 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 [...] > 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") > ] FWIW, I see these warnings as well. Any help from ppc developers is appreciated - should the R_PPC64_ADDR64 be whitelisted for exported asm symbols (their CRCs actually)? Thanks, Michal