From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Matt Wilson <msw@linux.com>
Cc: Konrad Rzeszutek Wilk <konrad@darnok.org>,
linux-kernel@vger.kernel.org,
Matthew Rushton <mrushton@amazon.com>,
david.vrabel@citrix.com, Matt Wilson <msw@amazon.com>,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] xen-blkback: bug fixes
Date: Tue, 4 Feb 2014 09:30:55 -0500 [thread overview]
Message-ID: <20140204143055.GA3853@phenom.dumpdata.com> (raw)
In-Reply-To: <20140204063139.GA19177@u109add4315675089e695.ant.amazon.com>
On Mon, Feb 03, 2014 at 10:31:40PM -0800, Matt Wilson wrote:
> On Tue, Jan 28, 2014 at 03:38:37PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, Jan 28, 2014 at 06:43:32PM +0100, Roger Pau Monne wrote:
> > > blkback bug fixes for memory leaks (patches 1 and 2) and a race
> > > (patch 3).
> >
> > They all look OK to me. I've stuck them in my 'stable/for-jens-3.14'
> > branch and are testing them now (hadn't pushed it yet).
> >
> > Matt and Matt,
> >
> > Could you take a look at the other two patches as well?
>
> Sure, though somehow you didn't address your message to us, so I
> didn't see it until today.
Duh!
>
> Matt Rushton did some review and testing on an earlier version that
> came out fine. We'll give the final series a test since there was
> still a bit of rework.
<nods>
>
> --msw
>
> > David, Boris,
> >
> > Are you OK with pushing those patches out to Jens Axboe if nobody
> > gives an NACK by Friday?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-02-04 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 17:43 xen-blkback: bug fixes Roger Pau Monne
2014-01-28 17:43 ` [PATCH 1/3] xen-blkback: fix memory leak when persistent grants are used Roger Pau Monne
2014-01-28 17:43 ` Roger Pau Monne
2014-01-28 17:43 ` Roger Pau Monne
2014-01-28 17:43 ` [PATCH 2/3] xen-blkback: fix memory leaks Roger Pau Monne
2014-01-28 17:43 ` Roger Pau Monne
2014-01-28 17:43 ` [PATCH 3/3] xen-blkback: fix shutdown race Roger Pau Monne
2014-01-28 17:43 ` Roger Pau Monne
2014-01-29 8:52 ` [Xen-devel] " Jan Beulich
2014-01-29 11:30 ` Roger Pau Monné
2014-01-29 11:30 ` Roger Pau Monné
2014-02-03 16:58 ` [Xen-devel] " Roger Pau Monné
2014-02-04 8:02 ` Jan Beulich
2014-02-04 8:02 ` [Xen-devel] " Jan Beulich
2014-02-04 8:16 ` Roger Pau Monné
2014-02-04 8:31 ` Jan Beulich
2014-02-04 8:31 ` [Xen-devel] " Jan Beulich
2014-02-04 8:39 ` Roger Pau Monné
2014-02-04 8:39 ` [Xen-devel] " Roger Pau Monné
2014-02-04 8:16 ` Roger Pau Monné
2014-02-03 16:58 ` Roger Pau Monné
2014-01-29 8:52 ` Jan Beulich
2014-01-28 19:38 ` [Xen-devel] xen-blkback: bug fixes Konrad Rzeszutek Wilk
2014-01-28 20:35 ` Boris Ostrovsky
2014-01-28 20:35 ` Boris Ostrovsky
2014-02-04 6:31 ` [Xen-devel] " Matt Wilson
2014-02-04 14:30 ` Konrad Rzeszutek Wilk [this message]
2014-02-04 14:30 ` Konrad Rzeszutek Wilk
2014-02-04 6:31 ` Matt Wilson
2014-01-28 19:38 ` Konrad Rzeszutek Wilk
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=20140204143055.GA3853@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mrushton@amazon.com \
--cc=msw@amazon.com \
--cc=msw@linux.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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.