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-next>] [day] [month] [year] [list]

Date:   Wed, 23 Jan 2019 11:56:01 -0800 (PST)
From:   Palmer Dabbelt <palmer@...ive.com>
To:     logang@...tatee.com
CC:     Christoph Hellwig <hch@...radead.org>, robh@...nel.org,
        dalias@...c.org, ysato@...rs.sourceforge.jp,
        linux-kernel@...r.kernel.org, sbates@...thlin.com,
        linux-riscv@...ts.infradead.org, Christoph Hellwig <hch@....de>,
        dan.j.williams@...el.com
Subject:    Re: [PATCH v4 1/2] sh: mm: make use of new memblocks_present() helper

On Tue, 15 Jan 2019 09:30:44 PST (-0800), logang@...tatee.com wrote:
>
>
> On 2019-01-15 6:58 a.m., Christoph Hellwig wrote:
>> Reviewed-by: Christoph Hellwig <hch@....de>
>>
>> Probably no need to keep this in a series with the RISC-V code, this can
>> be queued up by the sh folks independently.
>
> Oh, yeah, sorry, I obviously didn't pay enough attention to this when I
> resent it. I sent the similar Arm changes to the appropriate list and,
> yes, the sh ones should go to that maintainer.
>
> @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.