From: Richard Henderson <rth@twiddle.net>
To: Chen Gang <xili_gchen_5257@hotmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "walt@tilera.com" <walt@tilera.com>,
"Chris Metcalf" <cmetcalf@ezchip.com>,
"Riku Voipio" <riku.voipio@iki.fi>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3] Execute _start and reach to the first function call successfully
Date: Mon, 16 Mar 2015 08:37:56 -0700 [thread overview]
Message-ID: <5506F8D4.6090806@twiddle.net> (raw)
In-Reply-To: <BLU436-SMTP24722463C2927CA0D412CDBB9050@phx.gbl>
On 03/15/2015 04:57 PM, Chen Gang wrote:
> OK, thanks. And next, I shall try to send the whole tilegx patches again
> (it is about 6-8 patches), within 2015-03-18.
When you do so, make sure it's against the *current* master tree.
Your patch set doesn't compile at all at the moment, after
commit 2994fd96d986578a342f2342501b4ad30f6d0a85
Author: Eduardo Habkost <ehabkost@redhat.com>
Date: Thu Feb 26 17:37:49 2015 -0300
cpu: Make cpu_init() return QOM CPUState object
changed the return type of cpu_init.
In addition, one of your patches is going to need to copy over the linux
opcodes_tilegx.h header file. Perhaps you forgot to "git add" the file when
you created this "v3 Execute" patch?
r~
next prev parent reply other threads:[~2015-03-16 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 6:03 [Qemu-devel] [PATCH v3] Execute _start and reach to the first function call successfully Chen Gang
2015-03-15 23:45 ` Peter Maydell
2015-03-15 23:57 ` Chen Gang
2015-03-16 15:37 ` Richard Henderson [this message]
2015-03-17 23:02 ` Chen Gang
2015-03-16 15:31 ` Richard Henderson
2015-03-17 22:57 ` Chen Gang
[not found] <5503CF33.9070601@hotmail.com>
2015-03-15 14:19 ` Chen Gang
2015-03-15 16:50 ` Andreas Färber
2015-03-15 23:08 ` Chen Gang
2015-03-15 23:44 ` Peter Maydell
2015-03-15 23:52 ` Chen Gang
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=5506F8D4.6090806@twiddle.net \
--to=rth@twiddle.net \
--cc=afaerber@suse.de \
--cc=cmetcalf@ezchip.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=walt@tilera.com \
--cc=xili_gchen_5257@hotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.