From: Palmer Dabbelt <palmer@dabbelt.com>
To: jszhang3@mail.ustc.edu.cn
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Keep the riscv Kconfig selects sorted
Date: Tue, 24 Aug 2021 21:44:41 -0700 (PDT) [thread overview]
Message-ID: <mhng-43c0a2a8-fbd8-47bf-a9c4-4ac01333b6b0@palmerdabbelt-glaptop> (raw)
In-Reply-To: <20210805002908.2597836f@xhacker>
On Wed, 04 Aug 2021 09:29:08 PDT (-0700), jszhang3@mail.ustc.edu.cn wrote:
> From: Jisheng Zhang <jszhang@kernel.org>
>
> Move three Kconfig selects: ARCH_STACKWALK, ARCH_SUPPORTS_ATOMIC_RMW
> and ARCH_SUPPORTS_DEBUG_PAGEALLOC to the right place.
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> ---
> arch/riscv/Kconfig | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index 8fcceb8eda07..f133ac72572f 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -13,9 +13,6 @@ config 32BIT
> config RISCV
> def_bool y
> select ARCH_CLOCKSOURCE_INIT
> - select ARCH_SUPPORTS_ATOMIC_RMW
> - select ARCH_SUPPORTS_DEBUG_PAGEALLOC if MMU
> - select ARCH_STACKWALK
> select ARCH_HAS_BINFMT_FLAT
> select ARCH_HAS_DEBUG_VM_PGTABLE
> select ARCH_HAS_DEBUG_VIRTUAL if MMU
> @@ -33,6 +30,9 @@ config RISCV
> select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST
> select ARCH_OPTIONAL_KERNEL_RWX if ARCH_HAS_STRICT_KERNEL_RWX
> select ARCH_OPTIONAL_KERNEL_RWX_DEFAULT
> + select ARCH_STACKWALK
> + select ARCH_SUPPORTS_ATOMIC_RMW
> + select ARCH_SUPPORTS_DEBUG_PAGEALLOC if MMU
> select ARCH_SUPPORTS_HUGETLBFS if MMU
> select ARCH_USE_MEMTEST
> select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT if MMU
Thanks, this is on for-next.
prev parent reply other threads:[~2021-08-25 4:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 16:29 [PATCH] riscv: Keep the riscv Kconfig selects sorted Jisheng Zhang
2021-08-25 4:44 ` Palmer Dabbelt [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=mhng-43c0a2a8-fbd8-47bf-a9c4-4ac01333b6b0@palmerdabbelt-glaptop \
--to=palmer@dabbelt.com \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang3@mail.ustc.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.com \
/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;
as well as URLs for NNTP newsgroup(s).