From: Stefan Hajnoczi <stefanha@gmail.com>
To: Zhu Guihua <zhugh.fnst@cn.fujitsu.com>
Cc: qemu-devel@nongnu.org, tangchen@cn.fujitsu.com,
chen.fan.fnst@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
imammedo@redhat.com, guz.fnst@cn.fujitsu.com,
anshul.makkar@profitbricks.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support
Date: Thu, 5 Feb 2015 11:49:14 +0000 [thread overview]
Message-ID: <20150205114914.GA10126@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <cover.1421214154.git.zhugh.fnst@cn.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
On Wed, Jan 14, 2015 at 03:27:23PM +0800, Zhu Guihua wrote:
> This series is based on the previous patchset from Chen Fan:
> https://lists.nongnu.org/archive/html/qemu-devel/2014-05/msg02360.html
This email has an invalid charset:
Content-Type: text/plain; charset="y"
I guess you entered "y" when asked how the message was encoded.
Please don't do that, it means we can only guess at the charset.
Thanks,
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-02-05 11:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 7:27 [Qemu-devel] [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support Zhu Guihua
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 1/7] cpu: introduce CpuTopoInfo structure for argument simplification Zhu Guihua
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 2/7] qom/cpu: move register_vmstate to common CPUClass.realizefn Zhu Guihua
2015-01-29 14:04 ` Igor Mammedov
2015-02-09 8:30 ` Chen Fan
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 3/7] qom/cpu: move apic vmstate register into x86_cpu_apic_realize Zhu Guihua
2015-01-29 14:07 ` Igor Mammedov
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 4/7] monitor: use cc->get_arch_id as the cpu index Zhu Guihua
2015-01-29 14:12 ` Igor Mammedov
2015-01-29 14:21 ` Peter Krempa
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 5/7] acpi:cpu hotplug: set pcmachine as icc bus' hotplug handler Zhu Guihua
2015-01-29 14:18 ` Igor Mammedov
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 6/7] cpu: add device_add foo-x86_64-cpu support Zhu Guihua
2015-01-29 14:46 ` Igor Mammedov
2015-01-29 16:01 ` Eduardo Habkost
2015-01-29 16:39 ` Andreas Färber
2015-02-06 5:27 ` Chen Fan
2015-01-14 7:27 ` [Qemu-devel] [PATCH v3 7/7] i386/cpu: add instance finalize callback Zhu Guihua
2015-01-29 15:25 ` Igor Mammedov
2015-02-05 11:49 ` Stefan Hajnoczi [this message]
2015-02-05 15:25 ` [Qemu-devel] [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support Eric Blake
2015-02-05 19:29 ` Junio C Hamano
2015-02-05 19:57 ` Jeff King
2015-02-05 20:17 ` Junio C Hamano
2015-02-06 19:33 ` Jeff King
[not found] ` <CAMuHMdWbHMPEwkYvzKzzc6L0T8ufk62DGS2sZ1w1BthL1kAZWA@mail.gmail.com>
2015-02-16 22:34 ` [Qemu-devel] [PATCH] send-email: ask confirmation if given encoding name is very short Junio C Hamano
2015-02-18 18:58 ` Jeff King
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=20150205114914.GA10126@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=afaerber@suse.de \
--cc=anshul.makkar@profitbricks.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=tangchen@cn.fujitsu.com \
--cc=zhugh.fnst@cn.fujitsu.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).