From: Marc Zyngier <maz@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: tglx@linutronix.de, michal.simek@xilinx.com,
linux-kernel@vger.kernel.org, anirudh@xilinx.com
Subject: Re: [PATCH v2] irqchip/xilinx: Expose Kconfig option for Zynq/ZynqMP
Date: Tue, 20 Apr 2021 09:23:29 +0100 [thread overview]
Message-ID: <87h7k1qs8u.wl-maz@kernel.org> (raw)
In-Reply-To: <20210419194245.210550-1-robert.hancock@calian.com>
On Mon, 19 Apr 2021 20:42:45 +0100,
Robert Hancock <robert.hancock@calian.com> wrote:
>
> Previously the XILINX_INTC config option was hidden and only
> auto-selected on the MicroBlaze platform. However, this IP can also be
> used on the Zynq and ZynqMP platforms as a secondary cascaded
> controller. Allow this option to be user-enabled on those platforms.
>
> Signed-off-by: Robert Hancock <robert.hancock@calian.com>
> ---
> drivers/irqchip/Kconfig | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> index 15536e321df5..1020cc5a7800 100644
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -279,8 +279,13 @@ config XTENSA_MX
> select GENERIC_IRQ_EFFECTIVE_AFF_MASK
>
> config XILINX_INTC
> - bool
> + bool "Xilinx Interrupt Controller IP"
> + depends on MICROBLAZE || ARCH_ZYNQ || ARCH_ZYNQMP || COMPILE_TEST
Please drop COMPILE_TEST. As reported by the kernel test bot, there
are architectures it can't be compiled on.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2021-04-20 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 19:42 [PATCH v2] irqchip/xilinx: Expose Kconfig option for Zynq/ZynqMP Robert Hancock
2021-04-20 6:19 ` Michal Simek
2021-04-20 8:23 ` Marc Zyngier [this message]
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=87h7k1qs8u.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anirudh@xilinx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robert.hancock@calian.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.