qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: kwolf@redhat.com, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/3] block/nbd: merge nbd-client.* to nbd.c
Date: Thu, 13 Jun 2019 09:53:30 -0500	[thread overview]
Message-ID: <fad48964-b642-41a9-90e9-f26cdc8b34f2@redhat.com> (raw)
In-Reply-To: <20190611102720.86114-3-vsementsov@virtuozzo.com>


[-- Attachment #1.1: Type: text/plain, Size: 1704 bytes --]

On 6/11/19 5:27 AM, Vladimir Sementsov-Ogievskiy wrote:
> No reason of keeping driver handlers realization in separate of driver
> structure. We can get rid of extra header file.
> 
> While being here, fix comments style, restore forgotten comments for
> NBD_FOREACH_REPLY_CHUNK and nbd_reply_chunk_iter_receive, remove extra
> includes.

It's a little bit harder to review for accuracy when the patch does
cleanups at the same time; but this shows that the patch is fairly
simple to understand:

$ diff -u <(git log -p -1 | sed -n 's/^-//p') <(git log -p -1 | sed -n
's/^\+//p')

the most confusing parts were that HANDLE_TO_INDEX/INDEX_TO_HANDLE moved
differently from nbd_get_client_session(), and
nbd_client_{attach,detach}_aio_conext moved to a different relative
position.  Perhaps the patch could have been split to make the code
motion even easier to follow, but it's not worth respinning now.

> 
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
>  block/nbd-client.h  |   63 ---
>  block/nbd-client.c  | 1226 -----------------------------------------
>  block/nbd.c         | 1285 +++++++++++++++++++++++++++++++++++++++++--
>  block/Makefile.objs |    2 +-
>  block/trace-events  |    2 +-
>  5 files changed, 1255 insertions(+), 1323 deletions(-)
>  delete mode 100644 block/nbd-client.h
>  delete mode 100644 block/nbd-client.c

Reviewed-by: Eric Blake <eblake@redhat.com>

This will tend to cause merge conflicts to anything else touching either
file, so I plan to send a pull request soon.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-06-13 16:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 10:27 [Qemu-devel] [PATCH 0/3] nbd: merge block/nbd.c and block/nbd-client.c Vladimir Sementsov-Ogievskiy
2019-06-11 10:27 ` [Qemu-devel] [PATCH 1/3] block/nbd-client: drop stale logout Vladimir Sementsov-Ogievskiy
2019-06-13 14:28   ` Eric Blake
2019-06-11 10:27 ` [Qemu-devel] [PATCH 2/3] block/nbd: merge nbd-client.* to nbd.c Vladimir Sementsov-Ogievskiy
2019-06-13 14:53   ` Eric Blake [this message]
2019-06-11 10:27 ` [Qemu-devel] [PATCH 3/3] block/nbd: merge NBDClientSession struct back to BDRVNBDState Vladimir Sementsov-Ogievskiy
2019-06-13 15:16   ` Eric Blake
2019-06-13 15:20     ` Vladimir Sementsov-Ogievskiy
2019-06-13 16:06     ` Max Reitz

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=fad48964-b642-41a9-90e9-f26cdc8b34f2@redhat.com \
    --to=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.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).