qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>,
	Igor Mammedov <imammedo@redhat.com>,
	qemu-devel@nongnu.org, Haozhong Zhang <haozhong.zhang@intel.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	linux-nvdimm <linux-nvdimm@lists.01.org>,
	"Elliott, Robert (Persistent Memory)" <elliott@hpe.com>
Subject: Re: [Qemu-devel] [qemu PATCH v4 0/4] support NFIT platform capabilities
Date: Thu, 31 May 2018 16:03:42 -0600	[thread overview]
Message-ID: <20180531220342.GH28256@linux.intel.com> (raw)
In-Reply-To: <20180525205051-mutt-send-email-mst@kernel.org>

On Fri, May 25, 2018 at 08:51:22PM +0300, Michael S. Tsirkin wrote:
> On Mon, May 21, 2018 at 10:31:59AM -0600, Ross Zwisler wrote:
> > Changes since v3:
> >  * Updated the text in docs/nvdimm.txt to make it clear that the value
> >    being passed in on the command line in an integer made up of various
> >    bit fields. (Rob Elliott)
> >  
> >  * Updated the "Highest Valid Capability" byte to be dynamic based on
> >    the highest valid bit in the user's input. (Rob Elliott)
> 
> Igor could you review pls? I think your comments have been addressed.

Ping?  Igor, can you pick this up?

  reply	other threads:[~2018-05-31 22:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 16:31 [Qemu-devel] [qemu PATCH v4 0/4] support NFIT platform capabilities Ross Zwisler
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 1/4] nvdimm: fix typo in label-size definition Ross Zwisler
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 2/4] tests/.gitignore: add entry for generated file Ross Zwisler
2018-05-21 16:41   ` Eric Blake
2018-05-21 17:32     ` Philippe Mathieu-Daudé
2018-05-21 18:29       ` Eric Blake
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 3/4] nvdimm, acpi: support NFIT platform capabilities Ross Zwisler
2018-06-05 15:25   ` Michael S. Tsirkin
2018-06-05 16:42     ` Ross Zwisler
2018-06-05 18:15       ` Dan Williams
2018-06-05 18:37         ` Michael S. Tsirkin
2018-06-05 22:07           ` Ross Zwisler
2018-06-05 22:21             ` Dan Williams
2018-06-06 16:50               ` Ross Zwisler
2018-06-06 17:00                 ` Ross Zwisler
2018-06-06 17:08                   ` Ross Zwisler
2018-06-06 19:06                     ` Michael S. Tsirkin
2018-06-12 11:55                       ` Igor Mammedov
2018-06-06 19:04                   ` Michael S. Tsirkin
2018-06-06 19:07                 ` Michael S. Tsirkin
2018-06-06 23:20               ` Elliott, Robert (Persistent Memory)
2018-06-06 23:40                 ` Dan Williams
2018-06-07 15:29                   ` Michael S. Tsirkin
2018-06-07 15:30                 ` Michael S. Tsirkin
2018-05-21 16:32 ` [Qemu-devel] [qemu PATCH v4 4/4] ACPI testing: test " Ross Zwisler
2018-05-25 17:51 ` [Qemu-devel] [qemu PATCH v4 0/4] support " Michael S. Tsirkin
2018-05-31 22:03   ` Ross Zwisler [this message]
2018-05-29 19:54 ` Ross Zwisler
2018-06-01  5:11   ` Elliott, Robert (Persistent Memory)

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=20180531220342.GH28256@linux.intel.com \
    --to=ross.zwisler@linux.intel.com \
    --cc=ehabkost@redhat.com \
    --cc=elliott@hpe.com \
    --cc=haozhong.zhang@intel.com \
    --cc=imammedo@redhat.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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 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).