linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Date: Mon, 19 Jul 2021 16:22:05 +0900	[thread overview]
Message-ID: <YPUoHZ57b00bT0Hz@antec> (raw)
In-Reply-To: <96469a3e-82b5-f2b1-c0ea-5975e85332ce@infradead.org>

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

      reply	other threads:[~2021-07-19  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  2:23 [PATCH] openrisc: rename or32 code & comments to or1k Randy Dunlap
2021-07-16  6:11 ` kernel test robot
2021-07-19  4:39 ` Stafford Horne
2021-07-19  5:00   ` Randy Dunlap
2021-07-19  7:22     ` Stafford Horne [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YPUoHZ57b00bT0Hz@antec \
    --to=shorne@gmail.com \
    --cc=jonas@southpole.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openrisc@lists.librecores.org \
    --cc=rdunlap@infradead.org \
    --cc=stefan.kristiansson@saunalahti.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).