From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH v4 2/8] openrisc: Set CONFIG_MULTI_IRQ_HANDLER
Date: Thu, 29 Mar 2018 14:01:44 +0900 [thread overview]
Message-ID: <20180329050144.GD2836@lianli.shorne-pla.net> (raw)
In-Reply-To: <20180327161911.14086-3-palmer@sifive.com>
On Tue, Mar 27, 2018 at 09:19:05AM -0700, Palmer Dabbelt wrote:
> arm has an optional MULTI_IRQ_HANDLER, which openrisc copied but didn't
> make optional. I'm converting this to generic code, but in order to
> ensure everything stays bisectable I want this defined on openrisc for
> now. This will go away by the end of the patch set.
>
> Signed-off-by: Palmer Dabbelt <palmer@sifive.com>
Hi Palmer,
Thanks for doing this work, its always nice to see generic code pulled out of
architecture ports.
Acked-by: Stafford Horne <shorne@gmail.com>
> ---
> arch/openrisc/Kconfig | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/openrisc/Kconfig b/arch/openrisc/Kconfig
> index 339df7324e9c..9ecad05bfc73 100644
> --- a/arch/openrisc/Kconfig
> +++ b/arch/openrisc/Kconfig
> @@ -27,6 +27,7 @@ config OPENRISC
> select GENERIC_STRNLEN_USER
> select GENERIC_SMP_IDLE_THREAD
> select MODULES_USE_ELF_RELA
> + select MULTI_IRQ_HANDLER
> select HAVE_DEBUG_STACKOVERFLOW
> select OR1K_PIC
> select CPU_NO_EFFICIENT_FFS if !OPENRISC_HAVE_INST_FF1
> @@ -68,6 +69,9 @@ config STACKTRACE_SUPPORT
> config LOCKDEP_SUPPORT
> def_bool y
>
> +config MULTI_IRQ_HANDLER
> + def_bool y
> +
> source "init/Kconfig"
>
> source "kernel/Kconfig.freezer"
> --
> 2.16.1
>
next prev parent reply other threads:[~2018-03-29 5:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 16:19 [OpenRISC] Make set_handle_irq and handle_arch_irq generic, v4 Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 1/8] arm64: Set CONFIG_MULTI_IRQ_HANDLER Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 2/8] openrisc: " Palmer Dabbelt
2018-03-29 5:01 ` Stafford Horne [this message]
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 3/8] irq: Add CONFIG_GENERIC_IRQ_MULTI_HANDLER Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 4/8] RISC-V: Move to the new GENERIC_IRQ_MULTI_HANDLER handler Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 5/8] arm: Convert to GENERIC_IRQ_MULTI_HANDLER Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 6/8] arm64: Use the new GENERIC_IRQ_MULTI_HANDLER Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 7/8] openrisc: " Palmer Dabbelt
2018-03-27 16:19 ` [OpenRISC] [PATCH v4 8/8] irq: Remove MULTI_IRQ_HANDLER as it's now obselete Palmer Dabbelt
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=20180329050144.GD2836@lianli.shorne-pla.net \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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