qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] VMDK: remove debug output
Date: Wed, 25 Jun 2008 19:51:28 +0200	[thread overview]
Message-ID: <486285A0.2040304@reactos.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 165 bytes --]

Hi,

Attached patch removes some debug output from the VMDK block back-end.
In my opinion, only error messages have to be written to console.

Thanks

Hervé

[-- Attachment #2: vmdk_remove_debug.diff --]
[-- Type: text/plain, Size: 435 bytes --]

Index: block-vmdk.c
===================================================================
--- block-vmdk.c	(revision 4783)
+++ block-vmdk.c	(working copy)
@@ -376,7 +376,6 @@
     if (parent_open)
         // Parent must be opened as RO.
         flags = BDRV_O_RDONLY;
-    fprintf(stderr, "(VMDK) image open: flags=0x%x filename=%s\n", flags, bs->filename);
 
     ret = bdrv_file_open(&s->hd, filename, flags);
     if (ret < 0)

                 reply	other threads:[~2008-06-25 17:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=486285A0.2040304@reactos.org \
    --to=hpoussin@reactos.org \
    --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).