From: "Andreas Färber" <afaerber@suse.de>
To: Anthony Green <green@moxielogic.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Max Filippov <jcmvbkbc@gmail.com>,
Anthony Liguori <aliguori@amazon.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] ping.. Re: [PATCH moxie] Fix bug in tlb_fill.
Date: Sun, 15 Dec 2013 19:51:03 +0100 [thread overview]
Message-ID: <52ADFA17.2000109@suse.de> (raw)
In-Reply-To: <8761qqn496.fsf@moxielogic.com>
Hi,
Am 15.12.2013 05:10, schrieb Anthony Green:
>
> This patch still needs to be applied. There was some follow-up
> discussion on this patch back in May, but none of it negates the fact
> that this patch needs to be applied.
It introduces a tab, please fix.
Apart from that I believe I reported some inconsistencies between
targets in that function, so "all targets except moxie do it conditional
to FOO" may be a convincing explanation independent of the bug you were
discussing that may or may not be otherwise workaroundable.
And since this is purely in target-moxie I would suggest to simply send
a pull as target maintainer once you have someone trustworthy's
Reviewed-by and it doesn't break `make check`, similar to how it's done
for OpenRISC.
And as usual the warning that I have a patch lying around that changes
the cpu_loop_exit() argument to CPUState, but I may not get to rebasing
that until the holidays, so no imminent conflict.
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-12-15 18:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 20:04 [Qemu-devel] [PATCH moxie] Fix bug in tlb_fill Anthony Green
2013-05-13 20:33 ` Max Filippov
2013-05-14 16:02 ` Richard Henderson
2013-12-15 4:10 ` [Qemu-devel] ping.. " Anthony Green
2013-12-15 18:51 ` Andreas Färber [this message]
2013-12-15 19:03 ` Peter Maydell
2013-12-15 19:26 ` Anthony Green
2013-12-16 0:07 ` Peter Crosthwaite
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=52ADFA17.2000109@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=green@moxielogic.com \
--cc=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
/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).