linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-riscv@lists.infradead.org
Cc: Anup Patel <anup@brainfault.org>, Christoph Hellwig <hch@lst.de>,
	Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH] riscv: Fix use of undefined config option CONFIG_CONFIG_MMU
Date: Tue, 17 Dec 2019 12:15:16 +0100	[thread overview]
Message-ID: <mvmzhfr5hkr.fsf_-_@suse.de> (raw)
In-Reply-To: <mvm4kxz6xow.fsf@suse.de> (Andreas Schwab's message of "Tue, 17 Dec 2019 11:41:51 +0100")

In Kconfig files, config options are written without the CONFIG_ prefix.

Fixes: 6bd33e1ece52 ("riscv: add nommu support")
Signed-off-by: Andreas Schwab <schwab@suse.de>
---
 arch/riscv/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index b7fc77c0e860..298662e72572 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -156,7 +156,7 @@ config GENERIC_HWEIGHT
 	def_bool y
 
 config FIX_EARLYCON_MEM
-	def_bool CONFIG_MMU
+	def_bool MMU
 
 config PGTABLE_LEVELS
 	int
-- 
2.24.1

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."


  reply	other threads:[~2019-12-17 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 14:02 earlycon: earlycon_map: Couldn't map 0x0000000010010000 Andreas Schwab
2019-12-17 10:41 ` Andreas Schwab
2019-12-17 11:15   ` Andreas Schwab [this message]
2019-12-17 11:42     ` [PATCH] riscv: Fix use of undefined config option CONFIG_CONFIG_MMU Anup Patel
2019-12-17 18:12     ` Paul Walmsley

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=mvmzhfr5hkr.fsf_-_@suse.de \
    --to=schwab@suse.de \
    --cc=anup@brainfault.org \
    --cc=hch@lst.de \
    --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).