linux-kernel - Re: [PATCH] MIPS: perf: fix build failure

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: <20170626213218.GA5991@sudip-laptop>
Date:   Mon, 26 Jun 2017 22:32:18 +0100
From:   Sudip Mukherjee <sudipm.mukherjee@...il.com>
To:     Marcin Nowakowski <marcin.nowakowski@...tec.com>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Ralf Baechle <ralf@...ux-mips.org>,
        linux-kernel@...r.kernel.org, linux-mips@...ux-mips.org
Subject: Re: [PATCH] MIPS: perf: fix build failure

On Mon, Jun 26, 2017 at 08:44:48AM +0200, Marcin Nowakowski wrote:
> Hi Sudip,
> 
> This patch fixes the build error, but leaves the I6500 handling incorrect.

I am failing to understand why I6500 handling is incorrect. I am seeing
that after applying my patch the I6500 handling is same as introduced
by dd71e57bacb5.

> I had explained to Ralf how the build should be fixed a while ago so
> hopefully he will fix it up in his -next branch (dd71e57bacb5 should
> have been applied on top of f7a31b5e7874, but in Ralf's tree
> f7a31b5e7874 is applied on v4.12-rc4 while dd71e57bacb5 is applied
> on v4.12-rc2).

Ohh. ok. that explains. But then it should not have applied cleanly.

--
Regards
Sudip