All of lore.kernel.org
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@sifive.com>
To: j.neuschaefer@gmx.net
Cc: linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	j.neuschaefer@gmx.net, tglx@linutronix.de, jason@lakedaemon.net,
	maz@kernel.org
Subject: Re: [PATCH] irqchip: Place CONFIG_SIFIVE_PLIC into the menu
Date: Tue, 15 Oct 2019 09:31:43 -0700 (PDT)	[thread overview]
Message-ID: <mhng-f196bb74-ed87-41c9-98b9-a8161e663313@palmer-si-x1c4> (raw)
In-Reply-To: <20191002144452.10178-1-j.neuschaefer@gmx.net>

On Wed, 02 Oct 2019 07:44:52 PDT (-0700), j.neuschaefer@gmx.net wrote:
> Somehow CONFIG_SIFIVE_PLIC ended up outside of the "IRQ chip support"
> menu.
>
> Fixes: 8237f8bc4f6e ("irqchip: add a SiFive PLIC driver")
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
> ---
>  drivers/irqchip/Kconfig | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> index ccbb8973a324..97f9c001d8ff 100644
> --- a/drivers/irqchip/Kconfig
> +++ b/drivers/irqchip/Kconfig
> @@ -483,8 +483,6 @@ config TI_SCI_INTA_IRQCHIP
>  	  If you wish to use interrupt aggregator irq resources managed by the
>  	  TI System Controller, say Y here. Otherwise, say N.
>
> -endmenu
> -
>  config SIFIVE_PLIC
>  	bool "SiFive Platform-Level Interrupt Controller"
>  	depends on RISCV
> @@ -496,3 +494,5 @@ config SIFIVE_PLIC
>  	   interrupt sources are subordinate to the PLIC.
>
>  	   If you don't know what to do here, say Y.
> +
> +endmenu

Reviewed-by: Palmer Dabbelt <palmer@sifive.com>
Acked-by: Palmer Dabbelt <palmer@sifive.com>

I'm assuming this is going through the irqchip tree.

  reply	other threads:[~2019-10-15 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 14:44 [PATCH] irqchip: Place CONFIG_SIFIVE_PLIC into the menu Jonathan Neuschäfer
2019-10-15 16:31 ` Palmer Dabbelt [this message]
2019-11-11 10:50 ` Marc Zyngier
2019-11-20 13:21 ` [tip: irq/core] " tip-bot2 for Jonathan Neuschäfer

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=mhng-f196bb74-ed87-41c9-98b9-a8161e663313@palmer-si-x1c4 \
    --to=palmer@sifive.com \
    --cc=hch@lst.de \
    --cc=j.neuschaefer@gmx.net \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --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.