From: Stafford Horne <shorne@gmail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: openrisc@lists.librecores.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] openrisc: remove bogus nops and shutdowns
Date: Thu, 12 May 2022 05:54:18 +0900 [thread overview]
Message-ID: <YnwiepO0tBvt4hMe@antec> (raw)
In-Reply-To: <20220511133550.143236-1-Jason@zx2c4.com>
On Wed, May 11, 2022 at 03:35:50PM +0200, Jason A. Donenfeld wrote:
> Nop 42 is some leftover debugging thing by the looks of it. Nop 1 will
> shut down the simulator, which isn't what we want, since it makes it
> impossible to handle errors.
>
> Cc: Stafford Horne <shorne@gmail.com>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
Thanks, this looks good now. I will queue it.
prev parent reply other threads:[~2022-05-11 20:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 11:09 [PATCH] openrisc: remove bogus nops and shutdowns Jason A. Donenfeld
2022-05-04 22:24 ` Stafford Horne
2022-05-04 23:19 ` Jason A. Donenfeld
2022-05-11 13:35 ` [PATCH v2] " Jason A. Donenfeld
2022-05-11 20:54 ` 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=YnwiepO0tBvt4hMe@antec \
--to=shorne@gmail.com \
--cc=Jason@zx2c4.com \
--cc=linux-kernel@vger.kernel.org \
--cc=openrisc@lists.librecores.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).