Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 19 Jul 2021 16:22:05 +0900
From:   Stafford Horne <shorne@gmail.com>
To:     Randy Dunlap <rdunlap@infradead.org>
Cc:     linux-kernel@vger.kernel.org, Jonas Bonn <jonas@southpole.se>,
        Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
        openrisc@lists.librecores.org
Subject: Re: [PATCH] openrisc: rename or32 code & comments to or1k
Message-ID: <YPUoHZ57b00bT0Hz@antec>
References: <20210716022338.19342-1-rdunlap@infradead.org>
 <YPUCB7dSCHWrYHBl@antec>
 <96469a3e-82b5-f2b1-c0ea-5975e85332ce@infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <96469a3e-82b5-f2b1-c0ea-5975e85332ce@infradead.org>
Precedence: bulk

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