From: Jens Axboe <axboe@kernel.dk>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xensource.com
Cc: bob.liu@oracle.com
Subject: Re: [GIT PULL] (stable/for-jens-4.7) Xen block fixes for v4.7
Date: Thu, 9 Jun 2016 09:50:43 -0600 [thread overview]
Message-ID: <57599053.3070206@kernel.dk> (raw)
In-Reply-To: <20160609133417.GA15953@char.us.oracle.com>
On 06/09/2016 07:34 AM, Konrad Rzeszutek Wilk wrote:
> Hey Jens,
>
> Please git pull in your 'for-4.7/drivers' the following
> branch (based of your 'for-4.7/drivers):
>
> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.7
>
> which has two fixes for a guest migrating from host that
> has multi-queue to one without it (and vice-versa).
Pulled, thanks Konrad.
--
Jens Axboe
prev parent reply other threads:[~2016-06-09 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 13:34 [GIT PULL] (stable/for-jens-4.7) Xen block fixes for v4.7 Konrad Rzeszutek Wilk
2016-06-09 15:50 ` Jens Axboe [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=57599053.3070206@kernel.dk \
--to=axboe@kernel.dk \
--cc=bob.liu@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.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).