From: Andreas Schwab <schwab@linux-m68k.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: linux@roeck-us.net, alex@ghiti.fr, corbet@lwn.net,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, Arnd Bergmann <arnd@arndb.de>,
aryabinin@virtuozzo.com, glider@google.com, dvyukov@google.com,
linux-doc@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kasan-dev@googlegroups.com,
linux-arch@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v5 1/3] riscv: Move kernel mapping outside of linear mapping
Date: Thu, 17 Jun 2021 11:14:48 +0200 [thread overview]
Message-ID: <87czskonsn.fsf@igel.home> (raw)
In-Reply-To: <mhng-569bbfda-00d0-4c1f-9a88-69021f258f7e@palmerdabbelt-glaptop> (Palmer Dabbelt's message of "Wed, 16 Jun 2021 19:58:41 -0700 (PDT)")
On Jun 16 2021, Palmer Dabbelt wrote:
> This seems a long way off from defconfig. It's entirly possible I'm
> missing something, but at least CONFIG_SOC_VIRT is jumping out as
> something that's disabled in the SUSE config but enabled upstream.
None of the SOC configs are really needed, they are just convenience.
They can even be harmful, if they force a config to y if m is actually
wanted. Which is what happens with SOC_VIRT, which forces
RTC_DRV_GOLDFISH to y.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-06-17 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210611110019.GA579376@roeck-us.net>
2021-06-17 2:58 ` [PATCH v5 1/3] riscv: Move kernel mapping outside of linear mapping Palmer Dabbelt
2021-06-17 9:14 ` Andreas Schwab [this message]
2021-07-01 2:59 ` Palmer Dabbelt
[not found] <20210411164146.20232-2-alex@ghiti.fr>
2021-04-15 4:20 ` Palmer Dabbelt
2021-04-15 4:54 ` Alex Ghiti
2021-04-15 18:00 ` Alex Ghiti
2021-04-18 11:38 ` Alex Ghiti
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=87czskonsn.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=aryabinin@virtuozzo.com \
--cc=corbet@lwn.net \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=palmer@dabbelt.com \
--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).