From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: next-20160909 build: 1 failures 0 warnings (next-20160909) Date: Fri, 09 Sep 2016 12:56:46 +0200 Message-ID: <3281448.mbmBk67UZ8@wuerfel> References: <20160909101407.GA27946@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: Received: from mout.kundenserver.de ([212.227.126.131]:64726 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753820AbcIIK7X (ORCPT ); Fri, 9 Sep 2016 06:59:23 -0400 In-Reply-To: <20160909101407.GA27946@sirena.org.uk> Sender: linux-next-owner@vger.kernel.org List-ID: To: linaro-kernel@lists.linaro.org Cc: Mark Brown , Hoan Tran , Guenter Roeck , Jean Delvare , linux-hwmon@vger.kernel.org, linux-next@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel-build-reports@lists.linaro.org On Friday, September 9, 2016 11:14:07 AM CEST Mark Brown wrote: > On Fri, Sep 09, 2016 at 09:54:37AM +0100, Build bot for Mark Brown wrote: > > Since yesterday -next has been failing to build an arm64 allmodconfig > due to: > > > arm64-allmodconfig > > ERROR: "memblock_is_memory" [drivers/hwmon/xgene-hwmon.ko] undefined! > > caused by 05dbf57876b97d2 (hwmon: Add xgene hwmon driver). That symbol > is not exported so can't be used from modules though I can't immediately > see how that module acquired a reference to that symbol. See also https://lkml.org/lkml/2016/9/8/311 I haven't done a patch since we're still debating about how to best address this. Arnd