From: Kevin Wolf <kwolf@redhat.com>
To: Florian Florensa <fflorensa@online.net>
Cc: dillaman@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com,
mreitz@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH v3 0/1] block/rbd: Add support for ceph namespaces
Date: Thu, 5 Mar 2020 15:23:52 +0100 [thread overview]
Message-ID: <20200305142352.GB5363@linux.fritz.box> (raw)
In-Reply-To: <20200110111513.321728-1-fflorensa@online.net>
Am 10.01.2020 um 12:15 hat Florian Florensa geschrieben:
> Fixed the white space issue, no changes other than that.
>
> Florian Florensa (1):
> block/rbd: Add support for ceph namespaces
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2020-03-05 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 11:15 [PATCH v3 0/1] block/rbd: Add support for ceph namespaces Florian Florensa
2020-01-10 11:15 ` [PATCH v3 1/1] " Florian Florensa
2020-01-10 13:52 ` Stefano Garzarella
2020-01-10 14:13 ` Jason Dillaman
2020-02-03 11:17 ` Florian Florensa
2020-03-05 10:12 ` Florian Florensa
2020-03-05 14:23 ` 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=20200305142352.GB5363@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=dillaman@redhat.com \
--cc=fflorensa@online.net \
--cc=mreitz@redhat.com \
--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).