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: <mhng-bc5a03c7-1387-43e2-bd72-fb03e344e196@palmer-si-x1c4>
Date:   Tue, 19 Mar 2019 19:54:10 -0700 (PDT)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     logang@...tatee.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

On Tue, 19 Mar 2019 10:56:52 PDT (-0700), logang@...tatee.com wrote:
> 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?

It must have, sorry.  Is this what you're referring to?

    https://patchwork.kernel.org/patch/10754911/