From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: linux-block@vger.kernel.org, axboe@kernel.dk,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] (xen) stable/for-jens-4.12
Date: Tue, 18 Apr 2017 14:31:23 -0400 [thread overview]
Message-ID: <20170418183123.GA26293@char.us.oracle.com> (raw)
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.12
which is based on your 'for-4.12/block' branch. It has one fix - to emit an
uevent whenever the size of the guest disk image changes.
Please pull!
drivers/block/xen-blkfront.c | 3 +++
1 file changed, 3 insertions(+)
Marc Olson (1):
blkfront: add uevent for size change
next reply other threads:[~2017-04-18 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 18:31 Konrad Rzeszutek Wilk [this message]
2017-04-19 14:14 ` [GIT PULL] (xen) stable/for-jens-4.12 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2017-05-15 21:28 Konrad Rzeszutek Wilk
2017-05-15 21:33 ` 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=20170418183123.GA26293@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=axboe@kernel.dk \
--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).