[Qemu-devel] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path

Max Reitz posted 2 patches 5 years, 5 months ago
Test asan passed
Test checkpatch passed
Test docker-quick@centos7 passed
Test docker-mingw@fedora passed
Test docker-clang@ubuntu passed
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20181119101921.31949-1-mreitz@redhat.com
qemu-img.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
[Qemu-devel] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path
Posted by Max Reitz 5 years, 5 months ago
One of the amend error paths has two issues that are fixed by this
series.  Since they are relatively minor and have been present in 3.0
already, I think there is no need to get them into 3.1.  OTOH they are
bug fixes, so they could go into 3.1 if you, dear reader, insist.


Max Reitz (2):
  qemu-img: Fix typo
  qemu-img: Fix leak

 qemu-img.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
2.17.2


Re: [Qemu-devel] [Qemu-block] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path
Posted by John Snow 5 years, 5 months ago

On 11/19/18 5:19 AM, Max Reitz wrote:
> One of the amend error paths has two issues that are fixed by this
> series.  Since they are relatively minor and have been present in 3.0
> already, I think there is no need to get them into 3.1.  OTOH they are
> bug fixes, so they could go into 3.1 if you, dear reader, insist.

I enjoy your use of "dear reader" in cover letters.

Not related to the above:

Reviewed-by: John Snow <jsnow@redhat.com>

> 
> 
> Max Reitz (2):
>   qemu-img: Fix typo
>   qemu-img: Fix leak
> 
>  qemu-img.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 


Re: [Qemu-devel] [PATCH for-next? 0/2] qemu-img: Minor fixes to an amend error path
Posted by Kevin Wolf 5 years, 5 months ago
Am 19.11.2018 um 11:19 hat Max Reitz geschrieben:
> One of the amend error paths has two issues that are fixed by this
> series.  Since they are relatively minor and have been present in 3.0
> already, I think there is no need to get them into 3.1.  OTOH they are
> bug fixes, so they could go into 3.1 if you, dear reader, insist.

Thanks, applied to the block branch (looks like the dear reader
insists).

Kevin