From: "Michael S. Tsirkin" <mst@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org,
Xiao Guangrong <guangrong.xiao@linux.intel.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] docs: add document to explain the usage of vNVDIMM
Date: Mon, 21 Nov 2016 18:38:49 +0200 [thread overview]
Message-ID: <20161121183706-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20161121060023.524bgtem6mqsgacd@hz-desktop>
On Mon, Nov 21, 2016 at 02:00:23PM +0800, Haozhong Zhang wrote:
> On 11/09/16 12:35 +0000, Stefan Hajnoczi wrote:
> > On Wed, Nov 09, 2016 at 09:04:48AM +0800, Haozhong Zhang wrote:
> > > Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> > > Reviewed-by: Xiao Guangrong <guangrong.xiao@linux.intel.com>
> > > Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
> > > ---
> > > Changes since v1:
> > > * explicitly state the block window mode is not supported (Stefan Hajnoczi)
> > > * typo fix: label_size ==> label-size (David Alan Gilbert)
> > > ---
> > > docs/nvdimm.txt | 124 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > 1 file changed, 124 insertions(+)
> > > create mode 100644 docs/nvdimm.txt
> >
> > Great. This patch can go through Michael Tsirkin's tree alongside the
> > other current nvdimm patches.
>
> Hi Stefan and Michael,
>
> I noticed that Guangrong's patches had all been checked in. Will this
> doc patch be included in 2.8?
>
> Thanks,
> Haozhong
Given it was posted after soft freeze, I'd say no.
Pls remember to ping/repost after the release.
--
MST
next prev parent reply other threads:[~2016-11-21 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 1:04 [Qemu-devel] [PATCH v2] docs: add document to explain the usage of vNVDIMM Haozhong Zhang
2016-11-09 12:35 ` Stefan Hajnoczi
2016-11-21 6:00 ` Haozhong Zhang
2016-11-21 16:38 ` Michael S. Tsirkin [this message]
2016-11-22 0:10 ` Haozhong Zhang
2017-01-10 6:04 ` Haozhong Zhang
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=20161121183706-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dgilbert@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).