qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Leonardo E. Reiter" <lreiter@vbridges.com>
Cc: QEMU Developers Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/5] block: Virtual Bridges VERDE GOW disk image format, legacy GOW version 1 support implementation
Date: Fri, 09 Mar 2012 13:04:48 +0100	[thread overview]
Message-ID: <4F59F1E0.50205@redhat.com> (raw)
In-Reply-To: <CA+BHXkKGW-mfKVAw-F5YhsV7EHCObN4Z5TPUJbEaNOQGemTw2g@mail.gmail.com>

Am 08.03.2012 23:15, schrieb Leonardo E. Reiter:
> +BlockDriver bdrv_gow1 = {
> +    .format_name    = "gow1",
> +    .instance_size  = sizeof(gow1_state_t),
> +    .bdrv_probe     = gow1_probe,
> +    .bdrv_file_open = gow1_open,
> +    .bdrv_close     = gow1_close,
> +    .bdrv_read      = gow1_read,
> +    .bdrv_write     = gow1_write,
> +
> +    .bdrv_create    = gow1_create,
> +    .bdrv_getlength = gow1_getlength,
> +    .bdrv_truncate  = gow1_truncate,
> +    .create_options = gow1_create_options,
> +};

I wonder whether a name like verde_gow[123] wouldn't make more sense. I
think most people wouldn't be able to associate something with "gow",
and it doesn't look like a good keyword for searches either.

Also, is gow1 so different that implementing it in the same driver with
gow[23] would be impossible?

Kevin

  parent reply	other threads:[~2012-03-09 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 22:15 [Qemu-devel] [PATCH 3/5] block: Virtual Bridges VERDE GOW disk image format, legacy GOW version 1 support implementation Leonardo E. Reiter
2012-03-09 11:42 ` Stefan Hajnoczi
2012-03-09 11:59   ` Kevin Wolf
2012-03-09 12:04 ` Kevin Wolf [this message]
2012-03-09 14:35   ` Leonardo E. Reiter

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=4F59F1E0.50205@redhat.com \
    --to=kwolf@redhat.com \
    --cc=lreiter@vbridges.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).