From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753920AbdKGGBR (ORCPT ); Tue, 7 Nov 2017 01:01:17 -0500 Received: from mail-pg0-f44.google.com ([74.125.83.44]:44222 "EHLO mail-pg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753868AbdKGGBP (ORCPT ); Tue, 7 Nov 2017 01:01:15 -0500 X-Google-Smtp-Source: ABhQp+QRZUkT3nOYzFIVv/jU9cS4v9yydWHMIcV4+dzeXF7xVq1hj/hmo+WN9oSHj2gSynUkOPhLgA== Date: Mon, 6 Nov 2017 22:01:11 -0800 From: Bjorn Andersson To: Mark Brown Cc: Stephen Rothwell , Linux-Next Mailing List , Linux Kernel Mailing List , linux-kbuild@vger.kernel.org, "Yann E. MORIN" , linux-remoteproc@vger.kernel.org, Ohad Ben-Cohen Subject: Re: linux-next: build warning after merge of the regmap tree Message-ID: <20171107060111.GV28761@minitux> References: <20171106115214.19cb007a@canb.auug.org.au> <20171106152157.2ad9a5a9@canb.auug.org.au> <20171106153037.2afa3e7b@canb.auug.org.au> <20171106112143.ht4cmm2qngdbmmuy@sirena.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171106112143.ht4cmm2qngdbmmuy@sirena.co.uk> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 06 Nov 03:21 PST 2017, Mark Brown wrote: > On Mon, Nov 06, 2017 at 03:30:37PM +1100, Stephen Rothwell wrote: > > On Mon, 6 Nov 2017 15:21:57 +1100 Stephen Rothwell wrote: > > > On Mon, 6 Nov 2017 11:52:14 +1100 Stephen Rothwell wrote: > > > > > After merging the regmap tree, today's linux-next build > > > > (arm_multi_v7_defconfig) produced this warning: > [..] > isn't one right now. The root issue here is that HWSPINLOCK can be > built modular which makes it very painful to use from core code. I've picked Baolin's patch for making the hwspinlock core bool. Hopefully this help avoid this issue. Looks like I missed today's linux-next though. Regards, Bjorn