qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Дмитрий Фролов" <frolov@swemel.ru>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, fam@euphon.net,
	hreitz@redhat.com, sdl.qemu@linuxtesting.org
Subject: Re: [PATCH] fix bdrv_open_child return value check
Date: Fri, 1 Sep 2023 15:57:44 +0200	[thread overview]
Message-ID: <ZPHt2DzGsNeIg3w3@redhat.com> (raw)
In-Reply-To: <483510b6-dc31-c53c-b114-03aa249c3478@swemel.ru>

Am 01.09.2023 um 13:26 hat Дмитрий Фролов geschrieben:
> Hello, Kevin.
> 
> This was just cleanup, based on the inspection.

Thanks for clarifying. I've updated the subject line to "vmdk: Clean up
bdrv_open_child() return value check" to avoid misunderstandings and
applied this to my block branch.

Kevin



      reply	other threads:[~2023-09-01 13:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 12:59 [PATCH] fix bdrv_open_child return value check Dmitry Frolov
2023-09-01 11:15 ` Kevin Wolf
2023-09-01 11:26   ` Дмитрий Фролов
2023-09-01 13:57     ` Kevin Wolf [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=ZPHt2DzGsNeIg3w3@redhat.com \
    --to=kwolf@redhat.com \
    --cc=fam@euphon.net \
    --cc=frolov@swemel.ru \
    --cc=hreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sdl.qemu@linuxtesting.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).