| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20160504130236.12482401@canb.auug.org.au>
Date: Wed, 4 May 2016 13:02:36 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Noam Camus <noamc@...hip.com>,
Marc Zyngier <marc.zyngier@....com>
Subject: linux-next: manual merge of the tip tree with the arc tree
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/irqchip/Kconfig
between commit:
df1a714d52c4 ("irqchip: add nps Internal and external irqchips")
from the arc tree and commit:
9e2c986cb460 ("irqchip: Add per-cpu interrupt partitioning library")
from the tip tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/irqchip/Kconfig
index 1ab632a94db3,6c17de7997b9..000000000000
--- a/drivers/irqchip/Kconfig
+++ b/drivers/irqchip/Kconfig
@@@ -245,8 -246,5 +246,11 @@@ config MVEBU_ODM
bool
select GENERIC_MSI_IRQ_DOMAIN
+config EZNPS_GIC
+ bool "NPS400 Global Interrupt Manager (GIM)"
+ select IRQ_DOMAIN
+ help
+ Support the EZchip NPS400 global interrupt controller
++
+ config PARTITION_PERCPU
+ bool
Powered by blists - more mailing lists