From: Palmer Dabbelt <palmer@sifive.com>
To: atish.patra@wdc.com
Cc: Christoph Hellwig <hch@infradead.org>,
linux-riscv@lists.infradead.org, Damien.LeMoal@wdc.com,
anup@brainfault.org, linux-kernel@vger.kernel.org,
terpstra@sifive.com
Subject: Re: [PATCH] RISCV: Fix end PFN for low memory
Date: Tue, 25 Sep 2018 10:03:43 -0700 (PDT) [thread overview]
Message-ID: <mhng-133e3d9b-f580-40d4-bb7a-9cafa72fbb93@palmer-si-x1c4> (raw)
In-Reply-To: <50f35396-9e2b-c177-6a96-9c450c7abdde@wdc.com>
On Mon, 24 Sep 2018 13:55:04 PDT (-0700), atish.patra@wdc.com wrote:
> On 9/17/18 7:08 AM, Christoph Hellwig wrote:
>> 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?
>>
> Hi Palmer,
> I did not see this one pulled into your rc6 PR.
> Not sure if it was intentional or just lost in heap of emails.
Looks like it got lost, sorry. It's in my branch now, I might re-spin the rc6
PR because it looks like I may have screwed it up, if not I'll put it in rc7.
Thanks for the ping!
prev parent reply other threads:[~2018-09-25 17:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 18:30 [PATCH] RISCV: Fix end PFN for low memory Atish Patra
2018-09-17 14:08 ` Christoph Hellwig
2018-09-24 20:55 ` Atish Patra
2018-09-25 17:03 ` Palmer Dabbelt [this message]
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=mhng-133e3d9b-f580-40d4-bb7a-9cafa72fbb93@palmer-si-x1c4 \
--to=palmer@sifive.com \
--cc=Damien.LeMoal@wdc.com \
--cc=anup@brainfault.org \
--cc=atish.patra@wdc.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).