From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>,
Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block/ssh: Implement .bdrv_refresh_filename()
Date: Sat, 13 Apr 2019 18:26:23 +0200 [thread overview]
Message-ID: <81125c59-c2c8-6774-2daa-2a56ef204dbf@redhat.com> (raw)
In-Reply-To: <20190225190828.17726-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On 25.02.19 20:08, Max Reitz wrote:
> This series implements .bdrv_refresh_filename() for the ssh block
> driver, along with an appropriate .bdrv_dirname() so we don't chop off
> query strings for backing files with relative filenames.
>
>
> v3:
> - Keep iotests 104 and 207 working
>
>
> Max Reitz (2):
> block/ssh: Implement .bdrv_refresh_filename()
> block/ssh: Implement .bdrv_dirname()
>
> block/ssh.c | 73 ++++++++++++++++++++++++++++++++---
> tests/qemu-iotests/207 | 10 ++---
> tests/qemu-iotests/207.out | 10 ++---
> tests/qemu-iotests/common.rc | 2 +-
> tests/qemu-iotests/iotests.py | 2 +-
> 5 files changed, 80 insertions(+), 17 deletions(-)
Applied to my block-next branch.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org,
"Richard W . M . Jones" <rjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 0/2] block/ssh: Implement .bdrv_refresh_filename()
Date: Sat, 13 Apr 2019 18:26:23 +0200 [thread overview]
Message-ID: <81125c59-c2c8-6774-2daa-2a56ef204dbf@redhat.com> (raw)
Message-ID: <20190413162623.df9GUiOeq-a6b0PQrAEaS2p6V9vnxSKdEbPAJYP5b1o@z> (raw)
In-Reply-To: <20190225190828.17726-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On 25.02.19 20:08, Max Reitz wrote:
> This series implements .bdrv_refresh_filename() for the ssh block
> driver, along with an appropriate .bdrv_dirname() so we don't chop off
> query strings for backing files with relative filenames.
>
>
> v3:
> - Keep iotests 104 and 207 working
>
>
> Max Reitz (2):
> block/ssh: Implement .bdrv_refresh_filename()
> block/ssh: Implement .bdrv_dirname()
>
> block/ssh.c | 73 ++++++++++++++++++++++++++++++++---
> tests/qemu-iotests/207 | 10 ++---
> tests/qemu-iotests/207.out | 10 ++---
> tests/qemu-iotests/common.rc | 2 +-
> tests/qemu-iotests/iotests.py | 2 +-
> 5 files changed, 80 insertions(+), 17 deletions(-)
Applied to my block-next branch.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-13 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-25 19:08 [Qemu-devel] [PATCH v3 0/2] block/ssh: Implement .bdrv_refresh_filename() Max Reitz
2019-02-25 19:08 ` [Qemu-devel] [PATCH v3 1/2] " Max Reitz
2019-02-25 19:08 ` [Qemu-devel] [PATCH v3 2/2] block/ssh: Implement .bdrv_dirname() Max Reitz
2019-04-13 16:26 ` Max Reitz [this message]
2019-04-13 16:26 ` [Qemu-devel] [PATCH v3 0/2] block/ssh: Implement .bdrv_refresh_filename() Max Reitz
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=81125c59-c2c8-6774-2daa-2a56ef204dbf@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).