From: Christoph Hellwig <hch@infradead.org>
To: Atish Patra <atish.patra@wdc.com>
Cc: palmer@sifive.com, linux-riscv@lists.infradead.org,
Damien.LeMoal@wdc.com, anup@brainfault.org,
linux-kernel@vger.kernel.org, hch@infradead.org,
terpstra@sifive.com
Subject: Re: [PATCH] RISCV: Fix end PFN for low memory
Date: Mon, 17 Sep 2018 07:08:16 -0700 [thread overview]
Message-ID: <20180917140816.GA28689@infradead.org> (raw)
In-Reply-To: <1536690618-9157-1-git-send-email-atish.patra@wdc.com>
On Tue, Sep 11, 2018 at 11:30:18AM -0700, Atish Patra wrote:
> Use memblock_end_of_DRAM which provides correct last low memory
> PFN. Without that, DMA32 region becomes empty resulting in zero
> pages being allocated for DMA32.
>
> This patch is based on earlier patch from palmer which never
> merged into 4.19. I just edited the commit text to make more
> sense.
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
Palmer, can you queue this up for 4.19?
next prev parent reply other threads:[~2018-09-17 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 18:30 Atish Patra
2018-09-17 14:08 ` Christoph Hellwig [this message]
2018-09-24 20:55 ` Atish Patra
2018-09-25 17:03 ` Palmer Dabbelt
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=20180917140816.GA28689@infradead.org \
--to=hch@infradead.org \
--cc=Damien.LeMoal@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=terpstra@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
Powered by JetHome