From: Nick Clifton <nickc@redhat.com>
To: Stafford Horne <shorne@gmail.com>,
GDB patches <gdb-patches@sourceware.org>,
GNU Binutils <binutils@sourceware.org>
Cc: Andrey Bacherov <bandvig@mail.ru>,
Openrisc <openrisc@lists.librecores.org>
Subject: Re: [PATCH v2 2/6] opcodes: Regenerate opcodes for orfp64a32 spec
Date: Thu, 11 Apr 2019 08:45:00 -0000 [thread overview]
Message-ID: <c85d3576-d981-10c2-cf59-ab8447f4120d@redhat.com> (raw)
In-Reply-To: <20190409213925.32699-3-shorne@gmail.com>
Hi Stafford,
> opcodes/ChangeLog:
>
> * or1k-asm.c: Regenerated.
> * or1k-desc.c: Regenerated.
> * or1k-desc.h: Regenerated.
> * or1k-dis.c: Regenerated.
> * or1k-ibld.c: Regenerated.
> * or1k-opc.c: Regenerated.
> * or1k-opc.h: Regenerated.
> * or1k-opinst.c: Regenerated.
This part of your patch series is approved. Please commit whenever you are ready.
Cheers
Nick
next prev parent reply other threads:[~2019-04-11 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 21:39 [PATCH v2 0/6] OpenRISC orfpx64a32 support Stafford Horne
2019-04-09 21:39 ` [PATCH v2 1/6] cpu: Add support for orfp64a32 spec Stafford Horne
2019-04-09 21:39 ` [PATCH v2 4/6] sim/common: Wire in df/di conversion Stafford Horne
2019-04-13 21:59 ` Andrew Burgess
2019-04-09 21:40 ` [PATCH v2 3/6] sim/or1k: Regenerate sim for orfp64a32 spec Stafford Horne
2019-04-13 21:40 ` Andrew Burgess
2019-04-14 6:44 ` Stafford Horne
2019-04-09 21:40 ` [PATCH v2 5/6] sim/or1k: Add test for 64-bit fpu operations Stafford Horne
2019-04-13 21:36 ` Andrew Burgess
2019-04-09 21:40 ` [PATCH v2 2/6] opcodes: Regenerate opcodes for orfp64a32 spec Stafford Horne
2019-04-11 8:45 ` Nick Clifton [this message]
2019-04-09 21:40 ` [PATCH v2 6/6] sim/common: Fix issue with wrong byte order on BE targets Stafford Horne
2019-04-11 22:27 ` Andrew Burgess
2019-04-12 20:21 ` Stafford Horne
2019-04-13 21:30 ` Andrew Burgess
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=c85d3576-d981-10c2-cf59-ab8447f4120d@redhat.com \
--to=nickc@redhat.com \
--cc=bandvig@mail.ru \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=openrisc@lists.librecores.org \
--cc=shorne@gmail.com \
/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).