From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758926AbcILN1N (ORCPT ); Mon, 12 Sep 2016 09:27:13 -0400 Received: from mail-oi0-f42.google.com ([209.85.218.42]:35072 "EHLO mail-oi0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758759AbcILN1I (ORCPT ); Mon, 12 Sep 2016 09:27:08 -0400 MIME-Version: 1.0 In-Reply-To: <20160909143617.7106762e@canb.auug.org.au> References: <20160909143617.7106762e@canb.auug.org.au> From: Linus Walleij Date: Mon, 12 Sep 2016 15:27:07 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the gpio tree To: Stephen Rothwell Cc: "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Marc Zyngier 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 Fri, Sep 9, 2016 at 6:36 AM, Stephen Rothwell wrote: > After merging the gpio tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/gpio/gpiolib.c: In function '_gpiochip_irqchip_add': > drivers/gpio/gpiolib.c:1622:62: error: macro "WARN_ON" passed 3 arguments, but takes just 1 > "%s: Ignoring %d default trigger\n", of_node->full_name)) > ^ > drivers/gpio/gpiolib.c:1621:6: error: 'WARN_ON' undeclared (first use in this function) > if (WARN_ON(of_node && type != IRQ_TYPE_NONE, > ^ > > Caused by commit > > 1ded8b1dafe6 ("gpio/gpiolib: Forbid irqchip default trigger if probed over DT") > > I used the version of the gpio tree from next-20160908 for today. Sorry about this, fixed it up. Yours, Linus Walleij