All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam <shmuel.eiderman@oracle.com>
To: fam@euphon.net, kwolf@redhat.com, Max Reitz <mreitz@redhat.com>,
	qemu-block@nongnu.org
Cc: eyal.moscovici@oracle.com, Arbel Moshe <arbel.moshe@oracle.com>,
	yuchenlin@synology.com, qemu-devel@nongnu.org,
	liran.alon@oracle.com, Karl Heubaum <karl.heubaum@oracle.com>
Subject: Re: [Qemu-devel] [PATCH 0/2]: vmdk: Add read-only support for the new seSparse format
Date: Sun, 12 May 2019 11:14:21 +0300	[thread overview]
Message-ID: <7687F664-4BC3-47B9-A6CB-1B9B72ED80C2@oracle.com> (raw)
In-Reply-To: <20190424074901.31430-1-shmuel.eiderman@oracle.com>

Gentle ping on "[PATCH 2/2] vmdk: Add read-only support for seSparse snapshots”.
Yuchenlin reviewed "[PATCH 1/2] vmdk: Fix comment regarding max l1_size coverage”.

Thanks, Sam

> On 24 Apr 2019, at 10:48, Sam Eiderman <shmuel.eiderman@oracle.com> wrote:
> 
> VMware introduced a new snapshot format in VMFS6 - seSparse (Space
> Efficient Sparse) which is the default format available in ESXi 6.7.
> Add read-only support for the new snapshot format.
> 


  parent reply	other threads:[~2019-05-12  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  7:48 [Qemu-devel] [PATCH 0/2]: vmdk: Add read-only support for the new seSparse format Sam Eiderman
2019-04-24  7:48 ` Sam Eiderman
2019-04-24  7:49 ` [Qemu-devel] [PATCH 1/2] vmdk: Fix comment regarding max l1_size coverage Sam Eiderman
2019-04-24  7:49   ` Sam Eiderman
2019-04-24 10:19   ` [Qemu-devel] [Qemu-block] " yuchenlin
2019-04-24 10:19     ` yuchenlin via Qemu-devel
2019-04-24  7:49 ` [Qemu-devel] [PATCH 2/2] vmdk: Add read-only support for seSparse snapshots Sam Eiderman
2019-04-24  7:49   ` Sam Eiderman
2019-05-27 17:39   ` Max Reitz
2019-05-28  7:57     ` Sam Eiderman
2019-05-28 12:17       ` Max Reitz
2019-05-12  8:14 ` Sam [this message]
2019-05-27  8:26   ` [Qemu-devel] [PATCH 0/2]: vmdk: Add read-only support for the new seSparse format Sam Eiderman

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=7687F664-4BC3-47B9-A6CB-1B9B72ED80C2@oracle.com \
    --to=shmuel.eiderman@oracle.com \
    --cc=arbel.moshe@oracle.com \
    --cc=eyal.moscovici@oracle.com \
    --cc=fam@euphon.net \
    --cc=karl.heubaum@oracle.com \
    --cc=kwolf@redhat.com \
    --cc=liran.alon@oracle.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yuchenlin@synology.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.