From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jeff Cody <jcody@redhat.com>
Cc: qemu-block@nongnu.org, peter.maydell@linaro.org,
qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PULL for-2.8 0/1] Block patches for 2.8
Date: Tue, 22 Nov 2016 10:54:46 +0000 [thread overview]
Message-ID: <20161122105446.GC5970@stefanha-x1.localdomain> (raw)
In-Reply-To: <1479766499-29972-1-git-send-email-jcody@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Mon, Nov 21, 2016 at 05:14:58PM -0500, Jeff Cody wrote:
> The following changes since commit c36ed06e9159fa484b711dfdd27ec64d7ac3d17a:
>
> Merge remote-tracking branch 'mst/tags/for_upstream' into staging (2016-11-21 11:09:58 +0000)
>
> are available in the git repository at:
>
> https://github.com/codyprime/qemu-kvm-jtc.git tags/block-pull-request
>
> for you to fetch changes up to 668c0e441d761a79f33eae11c120e01a29f9d4dd:
>
> gluster: Fix use after free in glfs_clear_preopened() (2016-11-21 17:04:43 -0500)
>
> ----------------------------------------------------------------
> Block patches for 2.8
> ----------------------------------------------------------------
>
> Kevin Wolf (1):
> gluster: Fix use after free in glfs_clear_preopened()
>
> block/gluster.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> --
> 2.7.4
>
>
Thanks, applied to my staging tree:
https://github.com/stefanha/qemu/commits/staging
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2016-11-22 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 22:14 [Qemu-devel] [PULL for-2.8 0/1] Block patches for 2.8 Jeff Cody
2016-11-21 22:14 ` [Qemu-devel] [PULL for-2.8 1/1] gluster: Fix use after free in glfs_clear_preopened() Jeff Cody
2016-11-22 10:54 ` Stefan Hajnoczi [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=20161122105446.GC5970@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jcody@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).