From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
vsementsov@virtuozzo.com
Subject: [PATCH v3 0/6] block permission updated follow-up
Date: Tue, 1 Jun 2021 10:52:12 +0300 [thread overview]
Message-ID: <20210601075218.79249-1-vsementsov@virtuozzo.com> (raw)
v3:
02: add article
04: new
05: improve commit message, add assertion
06: rewrite error message
Based-on: Kevin's block branch
Vladimir Sementsov-Ogievskiy (6):
block: document child argument of bdrv_attach_child_common()
block-backend: improve blk_root_get_parent_desc()
block: improve bdrv_child_get_parent_desc()
block/vvfat: inherit child_vvfat_qcow from child_of_bds
block: simplify bdrv_child_user_desc()
block: improve permission conflict error message
block.c | 62 +++++++++++++++++----------
block/block-backend.c | 9 ++--
block/vvfat.c | 8 ++--
tests/qemu-iotests/283.out | 2 +-
tests/qemu-iotests/307.out | 2 +-
tests/qemu-iotests/tests/qsd-jobs.out | 2 +-
6 files changed, 50 insertions(+), 35 deletions(-)
--
2.29.2
next reply other threads:[~2021-06-01 7:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 7:52 Vladimir Sementsov-Ogievskiy [this message]
2021-06-01 7:52 ` [PATCH v3 1/6] block: document child argument of bdrv_attach_child_common() Vladimir Sementsov-Ogievskiy
2021-06-01 7:52 ` [PATCH v3 2/6] block-backend: improve blk_root_get_parent_desc() Vladimir Sementsov-Ogievskiy
2021-06-01 7:52 ` [PATCH v3 3/6] block: improve bdrv_child_get_parent_desc() Vladimir Sementsov-Ogievskiy
2021-06-01 7:52 ` [PATCH v3 4/6] block/vvfat: inherit child_vvfat_qcow from child_of_bds Vladimir Sementsov-Ogievskiy
2021-06-01 7:52 ` [PATCH v3 5/6] block: simplify bdrv_child_user_desc() Vladimir Sementsov-Ogievskiy
2021-06-01 7:52 ` [PATCH v3 6/6] block: improve permission conflict error message Vladimir Sementsov-Ogievskiy
2021-06-01 15:08 ` [PATCH v3 0/6] block permission updated follow-up 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=20210601075218.79249-1-vsementsov@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=kwolf@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).