[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55B74042.6070600@arm.com>
Date: Tue, 28 Jul 2015 09:41:38 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
"gregory.clement@...e-electrons.com"
<gregory.clement@...e-electrons.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
CC: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Jason Cooper <jason@...edaemon.net>,
"andrew@...n.ch" <andrew@...n.ch>,
Sudeep Holla <sudeep.holla@....com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Subject: Re: linux-next: build failure after merge of the tip tree
Hi Stephen,
On 28/07/15 03:43, Stephen Rothwell wrote:
> Hi all,
>
> After merging the tip tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/mach-mvebu/board-v7.c: In function 'mvebu_init_irq':
> arch/arm/mach-mvebu/board-v7.c:138:3: error: implicit declaration of function 'gic_set_irqchip_flags' [-Werror=implicit-function-declaration]
> gic_set_irqchip_flags(IRQCHIP_SKIP_SET_WAKE |
> ^
>
> Caused by commit
>
> e6f134f8e30e ("ARM: mvebu: Allow using the GIC for wakeup in standby mode")
>
> from the mvebu tree interacting with commit
>
> 0d3f2c92e004 ("irqchip/gic: Remove redundant gic_set_irqchip_flags")
>
> from the tip tree.
>
> I have applied the following merge fix patch for today:
>
Thanks for the fix, I was aware of this and asked Thomas Petazzoni
and Gregory CLEMENT to revert the commit e6f134f8e30e if possible
yesterday [1]
Regards,
Sudeep
[1]
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-July/359585.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists