Messages in this thread | | | Subject | Re: [PATCH v19 2/8] riscv/Kconfig: make direct map manipulation options depend on MMU | From | David Hildenbrand <> | Date | Fri, 14 May 2021 10:28:16 +0200 |
| |
On 13.05.21 20:47, Mike Rapoport wrote: > From: Mike Rapoport <rppt@linux.ibm.com> > > ARCH_HAS_SET_DIRECT_MAP and ARCH_HAS_SET_MEMORY configuration options have > no meaning when CONFIG_MMU is disabled and there is no point to enable > them for the nommu case. > > Add an explicit dependency on MMU for these options. > > Signed-off-by: Mike Rapoport <rppt@linux.ibm.com> > Reported-by: kernel test robot <lkp@intel.com> > --- > arch/riscv/Kconfig | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig > index a8ad8eb76120..c426e7d20907 100644 > --- a/arch/riscv/Kconfig > +++ b/arch/riscv/Kconfig > @@ -26,8 +26,8 @@ config RISCV > select ARCH_HAS_KCOV > select ARCH_HAS_MMIOWB > select ARCH_HAS_PTE_SPECIAL > - select ARCH_HAS_SET_DIRECT_MAP > - select ARCH_HAS_SET_MEMORY > + select ARCH_HAS_SET_DIRECT_MAP if MMU > + select ARCH_HAS_SET_MEMORY if MMU > select ARCH_HAS_STRICT_KERNEL_RWX if MMU && !XIP_KERNEL > select ARCH_HAS_STRICT_MODULE_RWX if MMU && !XIP_KERNEL > select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST >
Reviewed-by: David Hildenbrand <david@redhat.com>
-- Thanks,
David / dhildenb
| |