From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 1/2] block/qcow2.c: rename qcow_ functions to qcow2_
Date: Fri, 17 Dec 2010 15:37:51 +0100 [thread overview]
Message-ID: <4D0B75BF.1080001@redhat.com> (raw)
In-Reply-To: <4D0B719C.8010008@redhat.com>
On 12/17/10 15:20, Kevin Wolf wrote:
>> offset = start_offset;
>> while (offset < end_offset) {
>> @@ -88,13 +88,13 @@ static int qcow_read_extensions(BlockDriverState *bs, uint64_t start_offset,
>> #ifdef DEBUG_EXT
>> /* Sanity check */
>> if (offset > s->cluster_size)
>> - printf("qcow_handle_extension: suspicious offset %lu\n", offset);
>> + printf("qcow_read_extension: suspicious offset %lu\n", offset);
>
> It's now qcow2_read_extensions
Fixed
>> @@ -313,7 +313,7 @@ static int qcow_is_allocated(BlockDriverState *bs, int64_t sector_num,
>>
>> /* handle reading after the end of the backing file */
>> int qcow2_backing_read1(BlockDriverState *bs, QEMUIOVector *qiov,
>> - int64_t sector_num, int nb_sectors)
>> + int64_t sector_num, int nb_sectors)
>
> This isn't related to renaming functions. Please don't include pure
> formatting changes, all they do is making git blame work worse.
No it makes the formatting consistent with the rest of the functions in
the file. I can leave it out, but then we just have more ugliness in the
file.
>> @@ -399,10 +399,11 @@ static void qcow_aio_read_cb(void *opaque, int ret)
>> } else {
>> if (s->crypt_method) {
>> qcow2_encrypt_sectors(s, acb->sector_num, acb->cluster_data,
>> - acb->cluster_data, acb->cur_nr_sectors, 0, &s->aes_decrypt_key);
>> + acb->cluster_data, acb->cur_nr_sectors,
>> + 0, &s->aes_decrypt_key);
>
> Same here, plus the old version wasn't obviously indented wrong, but
> just not according to your personal style.
Sorry it's broken formatting. But sure, I'll put it back to being
unreadable.
> The following changes include more lines that need not be changed for
> the rename and just change the coding style (even though CODING_STYLE
> doesn't make a statement on this, so the old version isn't wrong).
> Please leave them out.
Actually that is in the patch, I did a pure search replace, no
formatting. But I've fixed it.
Jes
next prev parent reply other threads:[~2010-12-17 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 16:05 [Qemu-devel] [PATCH 0/2] qcow2 cleanups Jes.Sorensen
2010-12-16 16:05 ` [Qemu-devel] [PATCH 1/2] block/qcow2.c: rename qcow_ functions to qcow2_ Jes.Sorensen
2010-12-17 14:20 ` [Qemu-devel] " Kevin Wolf
2010-12-17 14:37 ` Jes Sorensen [this message]
2010-12-16 16:05 ` [Qemu-devel] [PATCH 2/2] Add proper -errno error return values to qcow2_open() Jes.Sorensen
2010-12-17 14:27 ` [Qemu-devel] " Kevin Wolf
2010-12-17 14:47 ` Jes Sorensen
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=4D0B75BF.1080001@redhat.com \
--to=jes.sorensen@redhat.com \
--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 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.