From: Paul Walmsley <paul.walmsley@sifive.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Anup Patel <anup@brainfault.org>,
linux-riscv@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] riscv: Fix use of undefined config option CONFIG_CONFIG_MMU
Date: Tue, 17 Dec 2019 10:12:15 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.21.9999.1912171012020.64438@viisi.sifive.com> (raw)
In-Reply-To: <mvmzhfr5hkr.fsf_-_@suse.de>
On Tue, 17 Dec 2019, Andreas Schwab wrote:
> 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>
Thanks Andreas, queued for v5.5-rc.
- Paul
prev parent reply other threads:[~2019-12-17 18:12 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 ` [PATCH] riscv: Fix use of undefined config option CONFIG_CONFIG_MMU Andreas Schwab
2019-12-17 11:42 ` Anup Patel
2019-12-17 18:12 ` Paul Walmsley [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=alpine.DEB.2.21.9999.1912171012020.64438@viisi.sifive.com \
--to=paul.walmsley@sifive.com \
--cc=anup@brainfault.org \
--cc=hch@lst.de \
--cc=linux-riscv@lists.infradead.org \
--cc=schwab@suse.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 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).