[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAhSdy1PRXpn-mgB0p4N-9q87xtWTwNPKJsUaGc6nTyz0ZsJug@mail.gmail.com>
Date: Mon, 25 Mar 2019 08:49:50 +0530
From: Anup Patel <anup@...infault.org>
To: Christoph Hellwig <hch@....de>
Cc: Anup Patel <Anup.Patel@....com>,
Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Atish Patra <Atish.Patra@....com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Christoph Hellwig <hch@...radead.org>,
Mike Rapoport <rppt@...ux.ibm.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RISC-V: Always compile mm/init.c with cmodel=medany
On Sun, Mar 24, 2019 at 8:27 PM Christoph Hellwig <hch@....de> wrote:
>
> On Sun, Mar 24, 2019 at 11:08:29AM +0000, Anup Patel wrote:
> > Signed-off-by: Christoph Hellwig <hch@....de>
> > Signed-off-by: Mike Rapoport <rppt@...ux.ibm.com>
>
> Huh? I don't think this is from Mike and me.
>
> > +unsigned long va_pa_offset;
> > +EXPORT_SYMBOL(va_pa_offset);
> > +unsigned long pfn_base;
> > +EXPORT_SYMBOL(pfn_base);
>
> Can you move va_pa_offset and pfn_base next to the swapper_pg_dir
> declaration? Thats where I move them in my current nommu patchset,
> as that allows to just have a single CONFIG_NOMMU in mm/init.c.
>
> Otherwise this looks fine to me.
Sure, no problem. I will send update and send v2.
Regards,
Anup
Powered by blists - more mailing lists