From: David Vrabel <david.vrabel@citrix.com>
To: "Jens Axboe" <axboe@fb.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
linux-kernel@vger.kernel.org,
xen-devel <xen-devel@lists.xenproject.org>,
"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Subject: Re: [GIT PULL] (xen) for-jens-3.20 for v3.20 Xen blk driver updates
Date: Tue, 10 Feb 2015 16:10:12 +0000 [thread overview]
Message-ID: <54DA2D64.4060901@citrix.com> (raw)
In-Reply-To: <54DA2367.8020200@fb.com>
On 10/02/15 15:27, Jens Axboe wrote:
> On 02/10/2015 05:58 AM, Roger Pau Monné wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hello Jens,
>>
>> There are 3 fixes for Xen blk drivers. One adds myself as a maintainer
>> (together with Konrad). There's also one to improve compatibility with
>> older xen-blkfront versions that did not specify a protocol version.
>> The remaining one is a fix for blkfront to correctly account the
>> number of requests on the queue when resuming from suspension.
>>
>> Thanks, Roger.
>>
>> The following changes since commit
>> e36f014edff70fc02b3d3d79cead1d58f289332e:
>>
>> Linux 3.19-rc7 (2015-02-01 20:07:21 -0800)
>>
>> are available in the git repository at:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-jens-3.20
>
> This is based on 3.19-rc7, which means that when I pulled it into
> for-3.20/drivers, I get a ton of unrelated commits as well.
Sorry Jens, that was my fault. I prepared the branch because Konrad has
been too busy and Roger doesn't have a kernel.org account yet.
I've now rebased this branch on your for-3.20/drivers branch.
David
next prev parent reply other threads:[~2015-02-10 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 12:58 [GIT PULL] (xen) for-jens-3.20 for v3.20 Xen blk driver updates Roger Pau Monné
2015-02-10 15:27 ` Jens Axboe
2015-02-10 16:10 ` David Vrabel [this message]
2015-02-10 16:12 ` Jens Axboe
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=54DA2D64.4060901@citrix.com \
--to=david.vrabel@citrix.com \
--cc=axboe@fb.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox