From: Kevin Wolf <kwolf@redhat.com>
To: Colin Lord <clord@redhat.com>
Cc: qemu-devel@nongnu.org, armbru@redhat.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Report error when opening device with locked tray
Date: Tue, 7 Jun 2016 12:28:50 +0200 [thread overview]
Message-ID: <20160607102850.GD4684@noname.str.redhat.com> (raw)
In-Reply-To: <1465242006-22509-1-git-send-email-clord@redhat.com>
Am 06.06.2016 um 21:40 hat Colin Lord geschrieben:
> This commit causes qmp_blockdev_change_medium to report an error if an
> attempt is made to open a device with a locked tray.
The old behaviour is that the command seemingly succeeds, but the medium
isn't actually changed. Correct?
Should this be mentioned in the commit message? You just describe what
you change, but not why.
> Signed-off-by: Colin Lord <clord@redhat.com>
> This is based off my previous patch regarding the do_open_tray function
> (currently at v3). Probably should have been submitted as a patch set
> but I wasn't thinking that far ahead when I submitted the first patch.
> ---
> blockdev.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
Yes, would probably have made sense as a series, but as long as it's
only two patches, it's not really a problem.
Please make sure to put such comments below the "---" line, though, i.e.
comments that make sense for the review, but not as part of the commit
log. Then git-am automatically removes that part from the commit message
while applying the patch. I did it manually for this one now.
Kevin
next prev parent reply other threads:[~2016-06-07 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 19:40 [Qemu-devel] [PATCH] Report error when opening device with locked tray Colin Lord
2016-06-07 10:28 ` Kevin Wolf [this message]
2016-06-07 20:00 ` [Qemu-devel] [Qemu-block] " John Snow
2016-06-08 8:20 ` Kevin Wolf
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=20160607102850.GD4684@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=clord@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).