qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Josh Durgin <jdurgin@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Jeff Cody <jcody@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 0/4] rbd cleanup and settings precedence fixes
Date: Tue, 14 Jul 2015 16:20:27 +0200	[thread overview]
Message-ID: <20150714142027.GA4219@noname.redhat.com> (raw)
In-Reply-To: <20150709095920.GA28530@stefanha-thinkpad.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1674 bytes --]

Am 09.07.2015 um 11:59 hat Stefan Hajnoczi geschrieben:
> On Tue, Jun 30, 2015 at 11:28:18AM -0700, Josh Durgin wrote:
> > Ping
> > 
> > On 06/10/2015 08:28 PM, Josh Durgin wrote:
> > >Patches 1 and 2 are simple cleanups. 3 and 4 fix the precedence of
> > >cache options and ceph settings. The cache option precedence in
> > >particular is important due to the potential for misconfigurations
> > >(ceph.conf setting rbd_cache=true, qemu setting cache=none) to
> > >accidentally put data at risk.
> > >
> > >Josh Durgin (4):
> > >   rbd: remove unused constants and fields
> > >   MAINTAINERS: update email address
> > >   rbd: make qemu's cache setting override any ceph setting
> > >   rbd: fix ceph settings precedence
> > >
> > >  MAINTAINERS |  2 +-
> > >  block/rbd.c | 64 +++++++++++++++++++++++++++++++++----------------------------
> > >  2 files changed, 36 insertions(+), 30 deletions(-)
> 
> This should go via Jeff:
> 
>   $ scripts/get_maintainer.pl -f block/rbd.c
>   Josh Durgin <josh.durgin@inktank.com> (supporter:RBD)
>   Jeff Cody <jcody@redhat.com> (supporter:RBD)
>   Kevin Wolf <kwolf@redhat.com> (supporter:Block layer core)
>   qemu-block@nongnu.org (open list:RBD)
> 
> Jeff is currently on vacation but will be back before the QEMU 2.4-rc1
> tag is made.

Considering that Josh is the primary maintainer for rbd and Jeff is just
merging patches for him, and that Jeff has already given R-b for patches
1 to 3, and that Jeff doesn't seem to be back yet, and that the patches
look good to me, I'm taking this through my tree for -rc1.

(I guess this is my longest "thanks, applied" sentence so far...)

Kevin

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2015-07-14 14:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11  3:28 [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-06-11  3:28 ` [Qemu-devel] [PATCH 1/4] rbd: remove unused constants and fields Josh Durgin
2015-06-30 19:47   ` Jeff Cody
2015-06-11  3:28 ` [Qemu-devel] [PATCH 2/4] MAINTAINERS: update email address Josh Durgin
2015-06-30 19:47   ` Jeff Cody
2015-06-11  3:28 ` [Qemu-devel] [PATCH 3/4] rbd: make qemu's cache setting override any ceph setting Josh Durgin
2015-06-30 19:47   ` Jeff Cody
2015-06-11  3:28 ` [Qemu-devel] [PATCH 4/4] rbd: fix ceph settings precedence Josh Durgin
2015-06-30 18:28 ` [Qemu-devel] [PATCH 0/4] rbd cleanup and settings precedence fixes Josh Durgin
2015-07-09  9:59   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2015-07-14 14:20     ` Kevin Wolf [this message]
2015-07-14 19:42       ` Josh Durgin

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=20150714142027.GA4219@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).