From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: axboe@kernel.dk, linux-block@vger.kernel.org,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Cc: jbeulich@suse.com
Subject: [GIT PULL] (xen-blkfront) stable/for-jens-4.10 for your 'linux-next' branch.
Date: Fri, 27 Jan 2017 13:47:43 -0500 [thread overview]
Message-ID: <20170127184743.GB31429@char.us.oracle.com> (raw)
Hey Jens,
Please pull in your 'for-linus' branch two little fixes for Xen
block front:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.10
One fix is for handling the XEN_PAGE_SIZE != PAGE_SIZE (4KB vs 64KB
on ARM for example) mishandling while the other is fixing
the accounting for the configuration changes.
Thank you!
drivers/block/xen-blkfront.c | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
Jan Beulich (2):
xen-blkfront: feature flags handling adjustments
xen-blkfront: correct maximum segment accounting
next reply other threads:[~2017-01-27 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 18:47 Konrad Rzeszutek Wilk [this message]
2017-01-27 18:57 ` [GIT PULL] (xen-blkfront) stable/for-jens-4.10 for your 'linux-next' branch 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=20170127184743.GB31429@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=axboe@kernel.dk \
--cc=jbeulich@suse.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