linux-kernel - Re: [PATCH v4 1/2] sh: mm: make use of new memblocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c9f13314-204b-10a5-e9eb-2c4d8fca6c90@deltatee.com>
Date:   Tue, 19 Mar 2019 11:56:52 -0600
From:   Logan Gunthorpe <logang@...tatee.com>
To:     Palmer Dabbelt <palmer@...ive.com>
Cc:     robh@...nel.org, dalias@...c.org, ysato@...rs.sourceforge.jp,
        dan.j.williams@...el.com, linux-kernel@...r.kernel.org,
        sbates@...thlin.com, Christoph Hellwig <hch@...radead.org>,
        linux-riscv@...ts.infradead.org, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper

Hey Palmer,

On 2019-01-23 12:56 p.m., Palmer Dabbelt wrote:
>> @Palmer: if you can just look at taking the second patch, I'll resubmit
>> the first one to the appropriate list.
> 
> Works for me.  I'll queue the second patch into my staging branch, targeted for
> the next merge window.

It doesn't look like my sparesmem patch made it into v5.1-rc1. Did it
fall through the cracks?

Thanks,

Logan