From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: pbonzini@redhat.com, imammedo@redhat.com, gleb@kernel.org,
mtosatti@redhat.com, stefanha@redhat.com, rth@twiddle.net,
ehabkost@redhat.com, dan.j.williams@intel.com,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v8 0/5] implement vNVDIMM
Date: Mon, 30 Nov 2015 20:33:26 +0800 [thread overview]
Message-ID: <565C4216.4090804@linux.intel.com> (raw)
In-Reply-To: <20151130123702-mutt-send-email-mst@redhat.com>
On 11/30/2015 06:38 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 16, 2015 at 06:50:58PM +0800, Xiao Guangrong wrote:
>> This patchset can be found at:
>> https://github.com/xiaogr/qemu.git nvdimm-v8
>>
>> It is based on pci branch on Michael's tree and the top commit is:
>> commit e3a4e177d9 (migration/ram: fix build on 32 bit hosts).
>>
>> Changelog in v8:
>> We split the long patch series into the small parts, as you see now, this
>> is the first part which enables NVDIMM without label data support.
>
> Finally found some time to review this. Very nice, this is making good
> progress, and I think to split it like this is a great idea. I sent
> some comments, most of them minor.
>
Thanks for your time and really happy to see you like it. :)
WARNING: multiple messages have this Message-ID (diff)
From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: ehabkost@redhat.com, kvm@vger.kernel.org, gleb@kernel.org,
mtosatti@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com,
imammedo@redhat.com, pbonzini@redhat.com,
dan.j.williams@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v8 0/5] implement vNVDIMM
Date: Mon, 30 Nov 2015 20:33:26 +0800 [thread overview]
Message-ID: <565C4216.4090804@linux.intel.com> (raw)
In-Reply-To: <20151130123702-mutt-send-email-mst@redhat.com>
On 11/30/2015 06:38 PM, Michael S. Tsirkin wrote:
> On Mon, Nov 16, 2015 at 06:50:58PM +0800, Xiao Guangrong wrote:
>> This patchset can be found at:
>> https://github.com/xiaogr/qemu.git nvdimm-v8
>>
>> It is based on pci branch on Michael's tree and the top commit is:
>> commit e3a4e177d9 (migration/ram: fix build on 32 bit hosts).
>>
>> Changelog in v8:
>> We split the long patch series into the small parts, as you see now, this
>> is the first part which enables NVDIMM without label data support.
>
> Finally found some time to review this. Very nice, this is making good
> progress, and I think to split it like this is a great idea. I sent
> some comments, most of them minor.
>
Thanks for your time and really happy to see you like it. :)
next prev parent reply other threads:[~2015-11-30 12:40 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 10:50 [PATCH v8 0/5] implement vNVDIMM Xiao Guangrong
2015-11-16 10:50 ` [Qemu-devel] " Xiao Guangrong
2015-11-16 10:50 ` [PATCH v8 1/5] nvdimm: implement NVDIMM device abstract Xiao Guangrong
2015-11-16 10:50 ` [Qemu-devel] " Xiao Guangrong
2015-11-16 10:51 ` [PATCH v8 2/5] acpi: support specified oem table id for build_header Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] " Xiao Guangrong
2015-11-16 10:51 ` [PATCH v8 3/5] nvdimm acpi: build ACPI NFIT table Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] " Xiao Guangrong
2015-11-30 10:30 ` Michael S. Tsirkin
2015-11-30 10:30 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-30 12:29 ` Xiao Guangrong
2015-11-30 12:29 ` [Qemu-devel] " Xiao Guangrong
2015-11-16 10:51 ` [PATCH v8 4/5] nvdimm acpi: build ACPI nvdimm devices Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] " Xiao Guangrong
2015-11-30 10:30 ` Michael S. Tsirkin
2015-11-30 10:30 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-30 12:21 ` Xiao Guangrong
2015-11-30 12:21 ` [Qemu-devel] " Xiao Guangrong
2015-11-30 10:32 ` Michael S. Tsirkin
2015-11-30 10:32 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-30 12:31 ` Xiao Guangrong
2015-11-30 12:31 ` [Qemu-devel] " Xiao Guangrong
2015-11-16 10:51 ` [PATCH v8 5/5] nvdimm: add maintain info Xiao Guangrong
2015-11-16 10:51 ` [Qemu-devel] " Xiao Guangrong
2015-11-18 1:59 ` [PATCH v8 0/5] implement vNVDIMM Xiao Guangrong
2015-11-18 1:59 ` [Qemu-devel] " Xiao Guangrong
2015-11-18 19:18 ` Eduardo Habkost
2015-11-18 19:18 ` [Qemu-devel] " Eduardo Habkost
2015-11-18 20:44 ` Michael S. Tsirkin
2015-11-18 20:44 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-19 2:39 ` Xiao Guangrong
2015-11-19 2:39 ` [Qemu-devel] " Xiao Guangrong
2015-11-19 8:21 ` Michael S. Tsirkin
2015-11-19 8:21 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-23 8:53 ` Stefan Hajnoczi
2015-11-23 8:53 ` [Qemu-devel] " Stefan Hajnoczi
2015-11-30 8:51 ` Stefan Hajnoczi
2015-11-30 8:51 ` [Qemu-devel] " Stefan Hajnoczi
2015-11-30 12:34 ` Xiao Guangrong
2015-11-30 12:34 ` [Qemu-devel] " Xiao Guangrong
2015-11-30 10:38 ` Michael S. Tsirkin
2015-11-30 10:38 ` [Qemu-devel] " Michael S. Tsirkin
2015-11-30 12:33 ` Xiao Guangrong [this message]
2015-11-30 12:33 ` Xiao Guangrong
2015-12-04 16:38 ` Vladimir Sementsov-Ogievskiy
2015-12-04 16:38 ` Vladimir Sementsov-Ogievskiy
2015-12-05 4:29 ` Xiao Guangrong
2015-12-05 4:29 ` [Qemu-devel] " Xiao Guangrong
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=565C4216.4090804@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=ehabkost@redhat.com \
--cc=gleb@kernel.org \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.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.