qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@fnarfbargle.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RESEND] [PATCH] Properly use backing file argument to qemu-img convert
Date: Tue, 04 Sep 2012 10:31:48 +0800	[thread overview]
Message-ID: <50456814.7010301@fnarfbargle.com> (raw)
In-Reply-To: <5044BD7D.3000706@suse.de>

On 03/09/12 22:23, Andreas Färber wrote:
> Am 03.09.2012 09:46, schrieb Brad Campbell:
>>   Converting to an image with an output backing file would write out the contents
>>   of the source image whether or not it was already contained in the new backing
>>   file. This commit ensures that the source file is checked against the new
>>   backing file and output is only allocated if it obsoletes or extends data
>>   already in the supplied backing file.
>>
>>
>> Signed-off-by: Brad Campbell <brad@fnarfbargle.com>
>
> For a resend it would've been nice to get the typos out, I'm sure you
> mean qemu-img. :) And it would be nice to have that marked as the topic
> then so that it's easily recognized ("qemu-img: Bla bla").

To be honest, with a typo that big I would never have picked it up 
myself no matter how many times I went over it. I'll take that 
suggestion for the topic, thanks.

>> ---
>>   qemu-img.c |   74 ++++++++++++++++++++++++++++++++++++++++++++++-------------
>>   1 files changed, 57 insertions(+), 17 deletions(-)
>>
>> diff --git a/qemu-img.c b/qemu-img.c
>> index c8a70ff..3fb6cbf 100644
>> --- a/qemu-img.c
>> +++ b/qemu-img.c
>> @@ -629,11 +629,12 @@ static int img_convert(int argc, char **argv)
>>       int progress = 0, flags;
>>       const char *fmt, *out_fmt, *cache, *out_baseimg, *out_filename;
>>       BlockDriver *drv, *proto_drv;
>> -    BlockDriverState **bs = NULL, *out_bs = NULL;
>> +    BlockDriverState **bs = NULL, *out_bs = NULL, *out_bf = NULL;
>>       int64_t total_sectors, nb_sectors, sector_num, bs_offset;
>> -    uint64_t bs_sectors;
>> +    uint64_t bf_sectors, bs_sectors;
>>       uint8_t * buf = NULL;
>>       const uint8_t *buf1;
>> +    uint8_t * bf_buf = NULL;
>
> Should be *bf_buf despite the * buf line above (checkpatch.pl sometimes
> mixes up multiplication and declaration of pointer variables).

I'll correct and re-send.

>>       BlockDriverInfo bdi;
>>       QEMUOptionParameter *param = NULL, *create_options = NULL;
>>       QEMUOptionParameter *out_baseimg_param;
> [snip]
>
> Note that the merge window for v1.3 is not yet open so you'll have to be
> a bit patient before seeing your patch in qemu.git.

I'm not in any hurry, it's just that the mail config on the machine I 
used git send-email from is so broken that the mail to Kevin bounced, so 
I waited a week before I re-sent it just to avoid bombing the list. As 
it turns out it's still broken anyway.

Thanks for the feedback.

Regards,
Brad

      reply	other threads:[~2012-09-04  2:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03  7:46 [Qemu-devel] [RESEND] [PATCH] Properly use backing file argument to git-img convert Brad Campbell
2012-09-03 14:23 ` Andreas Färber
2012-09-04  2:31   ` Brad Campbell [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=50456814.7010301@fnarfbargle.com \
    --to=brad@fnarfbargle.com \
    --cc=afaerber@suse.de \
    --cc=kwolf@redhat.com \
    --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).