From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: axboe@kernel.dk, linux-kernel@vger.kernel.org,
xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-jens-4.12
Date: Mon, 15 May 2017 17:28:46 -0400 [thread overview]
Message-ID: <20170515212846.GA18054@char.us.oracle.com> (raw)
Hey Jens,
Could you kindly pull:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.12
which has one tiny fix:
Thanks!
Gustavo A. R. Silva (1):
block: xen-blkback: add null check to avoid null pointer dereference
drivers/block/xen-blkback/xenbus.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
next reply other threads:[~2017-05-15 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-15 21:28 Konrad Rzeszutek Wilk [this message]
2017-05-15 21:33 ` [GIT PULL] (xen) stable/for-jens-4.12 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2017-04-18 18:31 Konrad Rzeszutek Wilk
2017-04-19 14:14 ` 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=20170515212846.GA18054@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=axboe@kernel.dk \
--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).