linux-kernel - Re: [PATCH] openrisc: rename or32 code & comments to or1k

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: <YPUoHZ57b00bT0Hz@antec>
Date:   Mon, 19 Jul 2021 16:22:05 +0900
From:   Stafford Horne <shorne@...il.com>
To:     Randy Dunlap <rdunlap@...radead.org>
Cc:     linux-kernel@...r.kernel.org, Jonas Bonn <jonas@...thpole.se>,
        Stefan Kristiansson <stefan.kristiansson@...nalahti.fi>,
        openrisc@...ts.librecores.org
Subject: Re: [PATCH] openrisc: rename or32 code & comments to or1k

On Sun, Jul 18, 2021 at 10:00:42PM -0700, Randy Dunlap wrote:
> On 7/18/21 9:39 PM, Stafford Horne wrote:
> > On Thu, Jul 15, 2021 at 07:23:38PM -0700, Randy Dunlap wrote:
> >> From Documentation/openrisc/todo.rst, rename "or32" in the
> >> source code to "or1k" since this is the name that has been
> >> settled on.
> > 
> > Hello, the kernel test robot found a build failure with this.
> > 
> > Will you send the update for that?
> > 
> 
> Hi,
> 
> The robot problems are not related to this patch (they were
> there before this patch), but I will send an update if you insist.

No problem,  I didn't investigate but just thought you had missed renaming
something.  In that case I will queue this and also look into fixing the robot
warning.

Thank you

-Stafford