[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mhng-99340121-50f8-49ca-ae6e-0f737fc4d736@palmerdabbelt-glaptop>
Date: Wed, 30 Jun 2021 19:59:09 -0700 (PDT)
From: Palmer Dabbelt <palmer@...belt.com>
To: schwab@...ux-m68k.org
CC: linux@...ck-us.net, alex@...ti.fr, corbet@....net,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, Arnd Bergmann <arnd@...db.de>,
aryabinin@...tuozzo.com, glider@...gle.com, dvyukov@...gle.com,
linux-doc@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-kernel@...r.kernel.org, kasan-dev@...glegroups.com,
linux-arch@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH v5 1/3] riscv: Move kernel mapping outside of linear mapping
On Thu, 17 Jun 2021 02:14:48 PDT (-0700), schwab@...ux-m68k.org wrote:
> 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.
Ya, in retrospect the SOC configs were really just a bad idea. I think
we've talked about removing them before as they break stuff, I just
haven't gotten around to doing it.
Powered by blists - more mailing lists