[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7747159.T9eeT0dC65@wuerfel>
Date: Tue, 09 Feb 2016 16:14:32 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Gregory CLEMENT <gregory.clement@...e-electrons.com>
Cc: Jason Cooper <jason@...edaemon.net>, Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
arm@...nel.org, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Jonathan Corbet <corbet@....net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, linux-serial@...r.kernel.org,
Tejun Heo <tj@...nel.org>, Hans de Goede <hdegoede@...hat.com>,
linux-ide@...r.kernel.org, linux-kernel@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
devicetree@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
linux-arm-kernel@...ts.infradead.org,
Lior Amsalem <alior@...vell.com>,
Nadav Haklai <nadavh@...vell.com>,
Omri Itach <omrii@...vell.com>
Subject: Re: [PATCH v3 01/12] irqchip: armada-370-xp: add Kconfig option for the driver
On Monday 08 February 2016 18:14:09 Gregory CLEMENT wrote:
>
> +config ARMADA_370_XP_IRQ
> + bool
> + default y if ARCH_MVEBU
> + select GENERIC_IRQ_CHIP
> +
>
Looks good. I wonder if we should also enable this for COMPILE_TEST, e.g.
config ARMADA_370_XP_IRQ
bool "Marvell Armada 3xx/XP/3xxx interrupt controller" if COMPILE_TEST && !ARCH_MVEBU
default ARCH_MVEBU
select GENERIC_IRQ_CHIP
If we do this, it's probably something outside of your series that we should
do for all patches, so don't worry about it here. Any opinions on the general
question?
Arnd
Powered by blists - more mailing lists