qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Pavel Hrdina <phrdina@redhat.com>
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] block: fix spurious DEVICE_TRAY_MOVED events on shutdown
Date: Thu, 30 May 2013 11:51:47 -0400	[thread overview]
Message-ID: <20130530115147.41fbd947@redhat.com> (raw)
In-Reply-To: <cover.1369841836.git.phrdina@redhat.com>

On Wed, 29 May 2013 18:18:17 +0200
Pavel Hrdina <phrdina@redhat.com> wrote:

> This fixes a regression introduced by commit 9ca111544.
> 
> The first commit is done by Luiz and I've just use it as it is.
> 
> The second commit moves the bdrv_dev_change_media_cb() into eject_device(),
> called by QMP and HMP eject command, and into qmp_bdrv_open_encrypted(),
> called by QMP and HMP change command. These are the only place where I think
> that should call the bdrv_dev_change_media_cb() function.
> 
> There is no reason to call this function while we are removing the device
> from the guest, for example while closing and deleting all devices on shutdown.

I'll defer review to the block guys, but as this works for me:

Tested-by: Luiz Capitulino <lcapitulino@redhat.com>

> 
> Luiz Capitulino (1):
>   block: make bdrv_dev_change_media_cb() public
> 
> Pavel Hrdina (1):
>   block: move the bdrv_dev_change_media_cb()
> 
>  block.c               | 11 +----------
>  blockdev.c            |  5 +++++
>  include/block/block.h |  1 +
>  3 files changed, 7 insertions(+), 10 deletions(-)
> 

      parent reply	other threads:[~2013-05-30 16:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-29 16:18 [Qemu-devel] [PATCH v2 0/2] block: fix spurious DEVICE_TRAY_MOVED events on shutdown Pavel Hrdina
2013-05-29 16:18 ` [Qemu-devel] [PATCH v2 1/2] block: make bdrv_dev_change_media_cb() public Pavel Hrdina
2013-05-29 16:18 ` [Qemu-devel] [PATCH v2 2/2] block: move the bdrv_dev_change_media_cb() Pavel Hrdina
2013-06-05 13:23   ` Stefan Hajnoczi
2013-06-17  9:46     ` Pavel Hrdina
2013-06-17 12:33       ` Stefan Hajnoczi
2013-06-17 13:22         ` Luiz Capitulino
2013-06-17 13:25           ` Pavel Hrdina
2013-06-17 13:32             ` Luiz Capitulino
2013-06-17 13:38               ` Pavel Hrdina
2013-06-17 13:46                 ` Luiz Capitulino
2013-06-17 13:46                 ` Kevin Wolf
2013-06-17 13:51                   ` Luiz Capitulino
2013-06-17 14:49                     ` Kevin Wolf
2013-06-17 14:59                       ` Luiz Capitulino
2013-06-17 15:16                         ` Kevin Wolf
2013-06-18  6:26                           ` Pavel Hrdina
2013-05-30 15:51 ` Luiz Capitulino [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=20130530115147.41fbd947@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=phrdina@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).