[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <mhng-291f78d2-5d90-4f44-8bbd-017264cd5be7@palmer-si-x1c4>
Date: Wed, 10 Apr 2019 10:13:34 -0700 (PDT)
From: Palmer Dabbelt <palmer@...ive.com>
To: anup@...infault.org
CC: Anup Patel <Anup.Patel@....com>, aou@...s.berkeley.edu,
Atish Patra <Atish.Patra@....com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Christoph Hellwig <hch@...radead.org>, rppt@...ux.ibm.com,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] RISC-V: Add separate defconfig for 32bit systems
On Tue, 09 Apr 2019 23:09:03 PDT (-0700), anup@...infault.org wrote:
> On Tue, Apr 9, 2019 at 10:14 PM Palmer Dabbelt <palmer@...ive.com> wrote:
>>
>> On Tue, 12 Mar 2019 15:08:12 PDT (-0700), Anup Patel wrote:
>> > This patch adds rv32_defconfig for 32bit systems. The only
>> > difference between rv32_defconfig and defconfig is that
>> > rv32_defconfig has CONFIG_ARCH_RV32I=y.
>>
>> Thanks. I think it makes sense to have this in 5.1 so I'm going to take it
>> into the next RC.
>
> Thanks, Palmer.
>
> Can you consider "[PATCH v3] RISC-V: Fix Maximum Physical Memory 2GiB
> option for 64bit systems" for 5.1?
>
> Refer, https://patchwork.kernel.org/patch/10886895/
>
> The above patch is also required for 64bit system with more than 128GiB memory
> (i.e. server-class system).
>
> We can remove "Maximum Physical Memory 2GiB" option as separate patch.
Ya, that should go in. It's on the branch, thanks for the reminder!
Powered by blists - more mailing lists