qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Pantelis Koukousoulas <pktoss@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add support for vmware vmdk scsi images to qemu-img
Date: Wed, 12 Aug 2009 15:48:15 +0200	[thread overview]
Message-ID: <4A82C81F.3000401@redhat.com> (raw)
In-Reply-To: <4A71EB4E.3070904@codemonkey.ws>

Anthony Liguori schrieb:
> Pantelis Koukousoulas wrote:
>> diff --git a/block_int.h b/block_int.h
>> index 830b7e9..0311198 100644
>> --- a/block_int.h
>> +++ b/block_int.h
>> @@ -30,10 +30,12 @@
>>  #define BLOCK_FLAG_ENCRYPT	1
>>  #define BLOCK_FLAG_COMPRESS	2
>>  #define BLOCK_FLAG_COMPAT6	4
>> +#define BLOCK_FLAG_SCSI         8
> 
> The flag space is limited and I don't want to pollute it with options 
> that are of no use to QEMU.  If you were able to limit the impact of 
> this patch to just block/vmdk.c, we would be more likely to consider 
> it.  That may require a greater refactoring of how options work though.

Well, yes, a refactoring as great as using a local int scsi instead of
defining a global constant to be or-ed into a local int flags... ;-)
Actually I think we could drop these global BLOCK_FLAG_* completely
without losing anything.

And otherwise the patch already is completely local to VMDK.

Kevin

      reply	other threads:[~2009-08-12 13:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-30 15:55 [Qemu-devel] [PATCH] Add support for vmware vmdk scsi images to qemu-img Pantelis Koukousoulas
2009-07-30 16:27 ` Paul Brook
2009-07-30 17:11   ` Pantelis Koukousoulas
2009-07-30 18:49 ` Anthony Liguori
2009-08-12 13:48   ` Kevin Wolf [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=4A82C81F.3000401@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=pktoss@gmail.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).