qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Add qerror message if the 'change' target filename can't be opened
Date: Thu, 1 Apr 2010 13:23:44 -0500	[thread overview]
Message-ID: <20100401182344.GV24351@us.ibm.com> (raw)
In-Reply-To: <20100401151551.443ba961@redhat.com>

* Luiz Capitulino <lcapitulino@redhat.com> [2010-04-01 13:17]:
> On Thu, 25 Mar 2010 09:32:58 -0500
> Ryan Harper <ryanh@us.ibm.com> wrote:
> 
> > Currently when using the change command to switch the file in the cd drive
> > the command doesn't complain if the file doesn't exit or can't be opened
> > and the drive keeps the existing image.  This patch adds a qerror_report
> > call to print a message out indicating the failure.  This error message
> > can be used to catch failures.
> 
>  Looks good to me, but it doesn't keep the existing image, it will silently
> eject it instead.

That's true, but that happens whether or not we indicate the change
failed.  I think fixing that is a good idea, but it shouldn't part of
this patch (just indicating the failure).


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
ryanh@us.ibm.com

  parent reply	other threads:[~2010-04-01 18:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 14:32 [Qemu-devel] [PATCH] Add qerror message if the 'change' target filename can't be opened Ryan Harper
2010-03-25 16:40 ` Markus Armbruster
2010-03-25 19:20   ` Ryan Harper
2010-03-25 19:42     ` Markus Armbruster
2010-04-01 18:15 ` Luiz Capitulino
2010-04-01 18:22   ` Luiz Capitulino
2010-04-01 19:14     ` Kevin Wolf
2010-04-01 20:55       ` Luiz Capitulino
2010-04-01 18:23   ` Ryan Harper [this message]
2010-04-01 18:31     ` Luiz Capitulino

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=20100401182344.GV24351@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=lcapitulino@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).