All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Subject: Re: [PATCH 0/3] block: fix the size change notification in bdrv_replace_child_bs()
Date: Tue, 17 Nov 2026 12:00:34 +0100	[thread overview]
Message-ID: <avwz0td5pLJ3TECD@redhat.com> (raw)
In-Reply-To: <20261105203752.3169635-1-den@openvz.org>

Am 05.11.2026 um 21:37 hat Denis V. Lunev geschrieben:
> These address Kevin's review of the series which went in through
> Eric's block pull as 8b267376df87..28fafb3147f5:
> https://lore.kernel.org/qemu-devel/auyju4uLIBaCGPKH@redhat.com/
> 
> Tested with a local qtest, not included: with a second scsi-hd sharing
> the new node, master reports CAPACITY DATA HAS CHANGED to that device
> after qom-set on the first one, and with patch 3 it does not.
> 
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Hanna Reitz <hreitz@redhat.com>
> Cc: Eric Blake <eblake@redhat.com>
> Cc: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>

Thanks, applied to the block branch.

Kevin



      parent reply	other threads:[~2026-11-17 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 20:37 [PATCH 0/3] block: fix the size change notification in bdrv_replace_child_bs() Denis V. Lunev
2026-11-05 20:37 ` [PATCH 1/3] block: read the old child length after draining " Denis V. Lunev
2026-11-05 20:37 ` [PATCH 2/3] block: add bdrv_child_notify_resize() to notify a single parent Denis V. Lunev
2026-11-05 20:37 ` [PATCH 3/3] block: notify only the replaced child in bdrv_replace_child_bs() Denis V. Lunev
2026-11-17 11:00 ` 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=avwz0td5pLJ3TECD@redhat.com \
    --to=kwolf@redhat.com \
    --cc=den@openvz.org \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=philmd@oss.qualcomm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.