From: sfr@canb.auug.org.au (Stephen Rothwell)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: build failure after merge of the tip tree
Date: Tue, 28 Jul 2015 12:43:24 +1000 [thread overview]
Message-ID: <20150728124324.40f44f01@canb.auug.org.au> (raw)
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:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 28 Jul 2015 12:26:21 +1000
Subject: [PATCH] irqchip/gic: merge fix for "Remove redundant gic_set_irqchip_flags"
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/arm/mach-mvebu/board-v7.c | 7 -------
1 file changed, 7 deletions(-)
diff --git a/arch/arm/mach-mvebu/board-v7.c b/arch/arm/mach-mvebu/board-v7.c
index a6d2b4d6701a..b5ef80f369e7 100644
--- a/arch/arm/mach-mvebu/board-v7.c
+++ b/arch/arm/mach-mvebu/board-v7.c
@@ -131,13 +131,6 @@ static int armada_375_external_abort_wa(unsigned long addr, unsigned int fsr,
static void __init mvebu_init_irq(void)
{
- struct device_node *np;
-
- np = of_find_compatible_node(NULL, NULL, "arm,cortex-a9-gic");
- if (np)
- gic_set_irqchip_flags(IRQCHIP_SKIP_SET_WAKE |
- IRQCHIP_MASK_ON_SUSPEND);
- of_node_put(np);
irqchip_init();
mvebu_scu_enable();
coherency_init();
--
2.4.6
--
Cheers,
Stephen Rothwell sfr at canb.auug.org.au
next reply other threads:[~2015-07-28 2:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 2:43 Stephen Rothwell [this message]
2015-07-28 8:41 ` linux-next: build failure after merge of the tip tree Sudeep Holla
2015-07-28 9:43 ` Gregory CLEMENT
-- strict thread matches above, loose matches on Subject: below --
2023-04-21 16:03 broonie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150728124324.40f44f01@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox