linux-kernel - Re: [PATCH] EDAC: mv64x60 calculate memory size correctly

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

Message-ID: <20170607090114.njdf4nve63rmz7yc@pd.tnic>
Date:   Wed, 7 Jun 2017 11:01:14 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Chris Packham <Chris.Packham@...iedtelesis.co.nz>
Cc:     "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "mchehab@...nel.org" <mchehab@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] EDAC: mv64x60 calculate memory size correctly

On Tue, Jun 06, 2017 at 09:19:04PM +0000, Chris Packham wrote:
> "mvebu" is the current trend for this family of orion/kirkwood/armada 
> SoCs. I can take mv64x60_edac.c and gut it to use as a base.

s/gut it/copy stuff for your own use in your *separate* driver/

Let's leave mv64x60_edac.c alone.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.