All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com,
	axboe@fb.com
Cc: bob.liu@oracle.com, roger.pau@citrix.com
Subject: Re: [GIT PULL] (xen) stable/for-jens-4.8-for-linus to your 'for-linus' branch for v4.8-rc3
Date: Fri, 19 Aug 2016 10:56:29 -0600	[thread overview]
Message-ID: <e15fac6c-0c35-f258-6039-4e57f21e7d47@kernel.dk> (raw)
In-Reply-To: <20160819164833.GA14691@char.us.oracle.com>

On 08/19/2016 10:48 AM, Konrad Rzeszutek Wilk wrote:
> Hey Jens!
>
> Please git pull the following three fixes in to your 'for-linus' branch.
> It is against 'for-linus' instead of 'for-4.8/drivers' because we had some
> code in xen-blkfront go through the Xen tree (with your Ack). The reason
> was that you 'for-4.8/drivers' was based on 4.7-rc2, and the fixes needed
> to be against newer tag.
>
> Anyhow, if you could please git pull the following branch:
>
>  git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.8-for-linus
>
> which has fixes as we are exercising the multiqueue components more aggressively.
>
> Here is the diffstat:
>
>  drivers/block/xen-blkfront.c | 97 +++++++++++++++++++++++++-------------------
>  1 file changed, 56 insertions(+), 41 deletions(-)
>
> Bob Liu (3):
>       xen-blkfront: fix places not updated after introducing 64KB page granularity
>       xen-blkfront: introduce blkif_set_queue_limits()
>       xen-blkfront: free resources if xlvbd_alloc_gendisk fails

Pulled, thanks.

-- 
Jens Axboe

      reply	other threads:[~2016-08-19 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 16:48 [GIT PULL] (xen) stable/for-jens-4.8-for-linus to your 'for-linus' branch for v4.8-rc3 Konrad Rzeszutek Wilk
2016-08-19 16:56 ` 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=e15fac6c-0c35-f258-6039-4e57f21e7d47@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=axboe@fb.com \
    --cc=bob.liu@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --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 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.