From: Jason A. Donenfeld <Jason@zx2c4.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [PATCH] hw/openrisc: use right OMPIC size variable
Date: Tue, 3 May 2022 11:59:57 +0200 [thread overview]
Message-ID: <YnD9HZNm0Sph1hLr@zx2c4.com> (raw)
In-Reply-To: <YnDzoWHqpYcCWTVs@antec>
On Tue, May 03, 2022 at 06:19:29PM +0900, Stafford Horne wrote:
> On Mon, May 02, 2022 at 04:59:47PM -0700, Richard Henderson wrote:
> > On 5/2/22 16:28, Jason A. Donenfeld wrote:
> > > This appears to be a copy and paste error. The UART size was used
> > > instead of the much smaller OMPIC size.
> > >
> > > Signed-off-by: Jason A. Donenfeld<Jason@zx2c4.com>
> > > ---
> > > hw/openrisc/openrisc_sim.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>
> Thanks,
>
> I will queue this one.
>
Please take a look at the v2 I posted instead.
next prev parent reply other threads:[~2022-05-03 9:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 23:28 [OpenRISC] [PATCH] hw/openrisc: use right OMPIC size variable Jason A. Donenfeld
2022-05-02 23:59 ` Richard Henderson
2022-05-03 9:19 ` Stafford Horne
2022-05-03 9:59 ` Jason A. Donenfeld [this message]
2022-05-03 9:45 ` [OpenRISC] [PATCH v2] " Jason A. Donenfeld
2022-05-03 20:22 ` Stafford Horne
2022-05-04 11:10 ` Jason A. Donenfeld
2022-05-04 22:23 ` Stafford Horne
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=YnD9HZNm0Sph1hLr@zx2c4.com \
--to=jason@zx2c4.com \
--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