qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 1/4] vmdk: Refactor vmdk_create_extent
Date: Fri, 7 Dec 2018 11:24:25 +0100	[thread overview]
Message-ID: <20181207102425.GA5119@linux.fritz.box> (raw)
In-Reply-To: <871s6t4z65.fsf@dusky.pond.sub.org>

Am 07.12.2018 um 07:40 hat Markus Armbruster geschrieben:
> Kevin Wolf <kwolf@redhat.com> writes:
> 
> > From: Fam Zheng <famz@redhat.com>
> >
> > The extracted vmdk_init_extent takes a BlockBackend object and
> > initializes the format metadata. It is the common part between "qemu-img
> > create" and "blockdev-create".
> >
> > Add a "BlockBackend *pbb" parameter to vmdk_create_extent, to return the
> > opened BB to the caller in the next patch.
> 
> I'd do this part in the next patch, when it has a user.  Matter of
> taste.

I kept Fam as the author of the patches (except for the test case which
is effectively a rewrite with Fam's test as the spec), so I'd like to
do only the minimal editing necessary to make the patches mergeable. If
it's a matter of taste, I'll leave it as it is.

The same goes for code changes that are a matter of taste: If you
_really_ care about taste in the vmdk code, feel free to send a
follow-up and I'll merge it on top, but I'll leave Fam's patches alone
as much as I can.

> Reviewed-by: Markus Armbruster <armbru@redhat.com>

Thanks!

Kevin

  reply	other threads:[~2018-12-07 10:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 15:13 [Qemu-devel] [PATCH v3 0/4] vmdk: Implement blockdev-create Kevin Wolf
2018-12-06 15:13 ` [Qemu-devel] [PATCH v3 1/4] vmdk: Refactor vmdk_create_extent Kevin Wolf
2018-12-07  6:40   ` Markus Armbruster
2018-12-07 10:24     ` Kevin Wolf [this message]
2018-12-07 12:52       ` Markus Armbruster
2018-12-06 15:13 ` [Qemu-devel] [PATCH v3 2/4] vmdk: Implement .bdrv_co_create callback Kevin Wolf
2018-12-07  7:10   ` Markus Armbruster
2018-12-07 10:53     ` Kevin Wolf
2018-12-07 12:57       ` Markus Armbruster
2018-12-06 15:13 ` [Qemu-devel] [PATCH v3 3/4] iotests: Filter cid numbers in VMDK extent info Kevin Wolf
2018-12-06 15:13 ` [Qemu-devel] [PATCH v3 4/4] iotests: Add VMDK tests for blockdev-create Kevin Wolf
2018-12-06 20:10 ` [Qemu-devel] [PATCH v3 0/4] vmdk: Implement blockdev-create no-reply

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=20181207102425.GA5119@linux.fritz.box \
    --to=kwolf@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).