From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751080AbdE2ILP (ORCPT ); Mon, 29 May 2017 04:11:15 -0400 Received: from mail-io0-f176.google.com ([209.85.223.176]:33833 "EHLO mail-io0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750787AbdE2ILN (ORCPT ); Mon, 29 May 2017 04:11:13 -0400 MIME-Version: 1.0 In-Reply-To: <20170529153947.458e2297@canb.auug.org.au> References: <20170529153947.458e2297@canb.auug.org.au> From: Linus Walleij Date: Mon, 29 May 2017 10:11:11 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the gpio tree To: Stephen Rothwell Cc: Linux-Next Mailing List , Linux Kernel Mailing List , Thomas Petazzoni , Gregory CLEMENT Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 29, 2017 at 7:39 AM, Stephen Rothwell wrote: > After merging the gpio tree, today's linux-next build (arm > orion5x_defconfig) failed like this: > > drivers/gpio/gpio-mvebu.c:1062: undefined reference to `__devm_regmap_init_mmio_clk' > drivers/gpio/gpio-mvebu.c:1078: undefined reference to `__devm_regmap_init_mmio_clk' > > Caused by commit > > 2233bf7a92e7 ("gpio: mvebu: switch to regmap for register access") > > Presumably a missing Kconfig dependency. Yeah, CONFIG_REGMAP_MMIO is > not set for this build. Yup Gregory sent a patch for this, I applied it, will be there tomorrow. Yours, Linus Walleij