From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: David Brenken <david.brenken@efs-auto.org>, qemu-devel@nongnu.org
Cc: Andreas Konopik <andreas.konopik@efs-auto.de>,
David Brenken <david.brenken@efs-auto.de>,
Robert Rasche <robert.rasche@efs-auto.de>,
Georg Hofstetter <georg.hofstetter@efs-auto.de>,
Lars Biermanski <lars.biermanski@efs-auto.de>
Subject: Re: [Qemu-devel] [PATCH v3 4/5] tricore: sync ctx.hflags with tb->flags
Date: Tue, 25 Jun 2019 12:00:54 +0200 [thread overview]
Message-ID: <5ab305b9-a527-f91c-38b0-12167d63a0da@mail.uni-paderborn.de> (raw)
In-Reply-To: <20190624070339.4408-5-david.brenken@efs-auto.org>
On 6/24/19 9:03 AM, David Brenken wrote:
> From: Georg Hofstetter <georg.hofstetter@efs-auto.de>
>
> Signed-off-by: Andreas Konopik <andreas.konopik@efs-auto.de>
> Signed-off-by: David Brenken <david.brenken@efs-auto.de>
> Signed-off-by: Georg Hofstetter <georg.hofstetter@efs-auto.de>
> Signed-off-by: Robert Rasche <robert.rasche@efs-auto.de>
> Signed-off-by: Lars Biermanski <lars.biermanski@efs-auto.de>
> ---
> target/tricore/translate.c | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
Cheers,
Bastian
next prev parent reply other threads:[~2019-06-25 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-24 7:03 [Qemu-devel] [PATCH v3 0/5] tricore: adding new instructions and fixing David Brenken
2019-06-24 7:03 ` [Qemu-devel] [PATCH v3 1/5] tricore: add FTOIZ instruction David Brenken
2019-06-24 7:03 ` [Qemu-devel] [PATCH v3 2/5] tricore: add UTOF instruction David Brenken
2019-06-24 7:03 ` [Qemu-devel] [PATCH v3 3/5] tricore: fix RRPW_INSERT instruction David Brenken
2019-06-24 7:03 ` [Qemu-devel] [PATCH v3 4/5] tricore: sync ctx.hflags with tb->flags David Brenken
2019-06-25 10:00 ` Bastian Koppelmann [this message]
2019-06-24 7:03 ` [Qemu-devel] [PATCH v3 5/5] tricore: add QSEED instruction David Brenken
2019-06-25 10:03 ` Bastian Koppelmann
2019-06-24 8:16 ` [Qemu-devel] [PATCH v3 0/5] tricore: adding new instructions and fixing no-reply
2019-06-24 9:05 ` no-reply
2019-06-25 10:04 ` Bastian Koppelmann
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=5ab305b9-a527-f91c-38b0-12167d63a0da@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=andreas.konopik@efs-auto.de \
--cc=david.brenken@efs-auto.de \
--cc=david.brenken@efs-auto.org \
--cc=georg.hofstetter@efs-auto.de \
--cc=lars.biermanski@efs-auto.de \
--cc=qemu-devel@nongnu.org \
--cc=robert.rasche@efs-auto.de \
/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).