From: John Snow <jsnow@redhat.com>
To: dillaman@redhat.com
Cc: Kevin Wolf <kwolf@redhat.com>, Josh Durgin <jdurgin@redhat.com>,
qemu-block <qemu-block@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v2] block/rbd: implement .bdrv_get_allocated_file_size callback
Date: Thu, 27 Jun 2019 15:45:48 -0400 [thread overview]
Message-ID: <90149c68-0dee-4afd-f517-5f204879dd18@redhat.com> (raw)
In-Reply-To: <CA+aFP1Btm6O5R0fiNZmBjHOO8t9ZDvvVgH0i1vFHsrQq85d+bA@mail.gmail.com>
On 6/27/19 3:43 PM, Jason Dillaman wrote:
> On Thu, Jun 27, 2019 at 1:24 PM John Snow <jsnow@redhat.com> wrote:
>>
>>
>>
>> On 6/27/19 4:48 AM, Stefano Garzarella wrote:
>>> On Wed, Jun 26, 2019 at 05:04:25PM -0400, John Snow wrote:
>>>> It looks like this has hit a 30 day expiration without any reviews or
>>>> being merged; do we still want this? If so, can you please resend?
>>>
>>> Yes, I think we still want :)
>>>
>>> Is it okay if I send a v3 following your comments?
>>>
>>
>> Yes, but I don't know who is responsible for final approval; I guess
>> that's Josh Durgin?
>
> I'm the new (for the past several years) upstream PTL for RBD, so feel
> free to tag me.
>
I got Josh's name out of MAINTAINERS, does it need an update?
> RBD
> M: Josh Durgin <jdurgin@redhat.com>
> L: qemu-block@nongnu.org
> S: Supported
> F: block/rbd.c
next prev parent reply other threads:[~2019-06-27 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 15:33 [Qemu-devel] [PATCH v2] block/rbd: implement .bdrv_get_allocated_file_size callback Stefano Garzarella
2019-06-26 21:04 ` [Qemu-devel] [Qemu-block] " John Snow
2019-06-27 8:48 ` Stefano Garzarella
2019-06-27 17:24 ` John Snow
2019-06-27 19:43 ` Jason Dillaman
2019-06-27 19:45 ` John Snow [this message]
2019-06-28 0:23 ` Jason Dillaman
2019-06-28 8:59 ` Stefano Garzarella
2019-07-02 15:09 ` Jason Dillaman
2019-07-03 7:31 ` Stefano Garzarella
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=90149c68-0dee-4afd-f517-5f204879dd18@redhat.com \
--to=jsnow@redhat.com \
--cc=dillaman@redhat.com \
--cc=jdurgin@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@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).