From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpFRo-0002pG-64 for qemu-devel@nongnu.org; Wed, 19 Jun 2013 06:17:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UpFRm-00087h-NP for qemu-devel@nongnu.org; Wed, 19 Jun 2013 06:17:04 -0400 Received: from mail-we0-x22b.google.com ([2a00:1450:400c:c03::22b]:39338) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UpFRm-00087a-HX for qemu-devel@nongnu.org; Wed, 19 Jun 2013 06:17:02 -0400 Received: by mail-we0-f171.google.com with SMTP id m46so4281544wev.16 for ; Wed, 19 Jun 2013 03:17:01 -0700 (PDT) Date: Wed, 19 Jun 2013 12:16:58 +0200 From: Stefan Hajnoczi Message-ID: <20130619101658.GA31475@stefanha-thinkpad.muc.redhat.com> References: <6c33b1e54320663db2ae9c606bde4cb13ca42928.1371474572.git.phrdina@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6c33b1e54320663db2ae9c606bde4cb13ca42928.1371474572.git.phrdina@redhat.com> Subject: Re: [Qemu-devel] [PATCH v3 2/2] block: move the bdrv_dev_change_media_cb() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pavel Hrdina Cc: kwolf@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com On Mon, Jun 17, 2013 at 03:21:41PM +0200, Pavel Hrdina wrote: > The bdrv_dev_change_media_cb() should be called only for eject and change > commands. We should call that function only if that command is successful. > > What this function does is that it calls the change_media_cb() and also emit > the QEVENT_DEVICE_TRAY_MOVED event. > > If a password is not required, but user provides some, the error is used as > warning. > > Signed-off-by: Pavel Hrdina > --- > block.c | 8 -------- > blockdev.c | 7 +++++++ > 2 files changed, 7 insertions(+), 8 deletions(-) This commit description explains what the code changes do but it doesn't explain why. The cover letter mentions a regression without going into detail, and that will not be commited to git. Please add information about the regression that this patch fixes so the git history has enough information to justify this patch. Markus posted a list of places that are affected by this change. Have you worked through them to show this patch is safe? Stefan