From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block: move I/O request processing to block/io.c
Date: Mon, 27 Apr 2015 10:26:45 -0600 [thread overview]
Message-ID: <553E6345.7060001@redhat.com> (raw)
In-Reply-To: <1430149991-29850-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On 04/27/2015 09:53 AM, Stefan Hajnoczi wrote:
> Note: This series is based on my block-next branch:
> https://github.com/stefanha/qemu.git block-next
>
> This series splits block.c because the file has grown too large. This helps
> separate the core block layer into BlockDriverState graph operations and I/O
> processing.
>
> Stefan Hajnoczi (2):
> block: replace bdrv_states iteration with bdrv_next()
> block: move I/O request processing to block/io.c
>
> block.c | 2519 +--------------------------------------------
> block/Makefile.objs | 2 +-
> include/block/block_int.h | 12 +
> 3 files changed, 18 insertions(+), 2515 deletions(-)
Umm, did you forget to 'git add block/io.c'?
The diffstat makes it look like you are deleting code, not splitting it.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-04-27 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 15:53 [Qemu-devel] [PATCH v3 0/2] block: move I/O request processing to block/io.c Stefan Hajnoczi
2015-04-27 15:53 ` [Qemu-devel] [PATCH v3 1/2] block: replace bdrv_states iteration with bdrv_next() Stefan Hajnoczi
2015-04-27 16:09 ` [Qemu-devel] [Qemu-block] " Alberto Garcia
2015-04-27 15:53 ` [Qemu-devel] [PATCH v3 2/2] block: move I/O request processing to block/io.c Stefan Hajnoczi
2015-04-27 16:28 ` Eric Blake
2015-04-27 16:26 ` Eric Blake [this message]
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=553E6345.7060001@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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).