From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhong Yang <yang.zhong@intel.com>
Cc: qemu-devel@nongnu.org, eblake@redhat.com,
laurent.desnogues@gmail.com, Xu@yangzhon-Virtual,
Anthony <anthony.xu@intel.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/4] tcg: split the tcg code and separate tcg files
Date: Thu, 8 Jun 2017 12:43:09 +0200 [thread overview]
Message-ID: <b2f54a70-0169-35ed-6e55-46dccd4ee41e@redhat.com> (raw)
In-Reply-To: <20170608085503.GA21945@yangzhon-Virtual>
On 08/06/2017 10:55, Zhong Yang wrote:
>>>
>> Queued, thanks (except I'm not sure why you're moving exec.c, so I've
>> undone that, and tcg-runtime.c probably fits better in tcg/).
>>
> Thanks Paolo for your great help!
>
> As for exec.c, i ever thought this file is related with system and moved here.
If we do that, there would many more files to move (e.g. ioport.c,
memory.c, user-exec.c). I think it's better to leave exec.c in the root
for now.
> You are right, since tcg-runtime.c is BSD Licenced, it should be moved to
> tcg/. Whether can i release V4 to do this moving?
Don't worry, I can do the moving.
Paolo
prev parent reply other threads:[~2017-06-08 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 6:06 [Qemu-devel] [PATCH v3 0/4] tcg: split the tcg code and separate tcg files Yang Zhong
2017-06-02 6:06 ` [Qemu-devel] [PATCH v3 1/4] accel: split the tcg accelerator from accel.c file Yang Zhong
2017-06-02 6:06 ` [Qemu-devel] [PATCH v3 2/4] tcg: move tcg related files into accel/tcg/ subdirectory Yang Zhong
2017-06-02 6:06 ` [Qemu-devel] [PATCH v3 3/4] tcg: move tcg backend files into accel/tcg/ Yang Zhong
2017-06-02 6:06 ` [Qemu-devel] [PATCH v3 4/4] accel: move kvm related accelerator files into accel/ Yang Zhong
2017-06-07 13:28 ` [Qemu-devel] [PATCH v3 0/4] tcg: split the tcg code and separate tcg files Paolo Bonzini
2017-06-08 9:19 ` Zhong Yang
[not found] ` <20170608085503.GA21945@yangzhon-Virtual>
2017-06-08 10:43 ` Paolo Bonzini [this message]
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=b2f54a70-0169-35ed-6e55-46dccd4ee41e@redhat.com \
--to=pbonzini@redhat.com \
--cc=Xu@yangzhon-Virtual \
--cc=anthony.xu@intel.com \
--cc=eblake@redhat.com \
--cc=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=yang.zhong@intel.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 NNTP newsgroup(s).