All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com>
Cc: Pradeep Jagadeesh <pradeepkiruvale@gmail.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Alberto Garcia <berto@igalia.com>,
	qemu-devel@nongnu.org,
	Claudio Fontana <claudio.fontana@huawei.com>
Subject: Re: [Qemu-devel] [V7 1/1] fsdev: add IO throttle support to fsdev devices
Date: Sun, 30 Oct 2016 17:35:59 +0100	[thread overview]
Message-ID: <20161030173559.3d0f14a1@bahia> (raw)
In-Reply-To: <ce2c3d63-cd32-7379-8706-c4afad0c3928@huawei.com>

On Sun, 30 Oct 2016 15:02:17 +0100
Pradeep Jagadeesh <pradeep.jagadeesh@huawei.com> wrote:

> On 10/30/2016 2:35 PM, Greg Kurz wrote:
[...]
> >
> > I'll be AFK most of tomorrow and soft freeze starts next Tuesday... do you
> > *really* need this to be in 2.8 ?
> >  
> If everything is OK, then we can push into 2.8.

I'm ok to issue a pull request before feature soft freeze if the patch looks
ok to me and it gets a R-b from Berto.

> When is the next release?.
> 

Don't know yet... very rough estimate would be end of March or April next year
I guess.

> -Pradeep

Cheers.

--
Greg

      reply	other threads:[~2016-10-30 16:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22 15:07 [Qemu-devel] [V7 1/1] fsdev: add IO throttle support to fsdev devices Pradeep Jagadeesh
2016-10-24 13:00 ` Alberto Garcia
2016-10-25  9:37   ` Pradeep Jagadeesh
2016-10-30 12:29     ` Pradeep Jagadeesh
2016-10-24 21:21 ` Greg Kurz
2016-10-24 21:28 ` Greg Kurz
2016-10-25  9:39   ` Pradeep Jagadeesh
2016-10-30 13:04     ` Pradeep Jagadeesh
2016-10-30 13:35       ` Greg Kurz
2016-10-30 14:02         ` Pradeep Jagadeesh
2016-10-30 16:35           ` Greg Kurz [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=20161030173559.3d0f14a1@bahia \
    --to=groug@kaod.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=berto@igalia.com \
    --cc=claudio.fontana@huawei.com \
    --cc=pradeep.jagadeesh@huawei.com \
    --cc=pradeepkiruvale@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.