qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PULL 0/1] UUID test fix patch for 2.8
Date: Mon, 14 Nov 2016 15:38:14 +0000	[thread overview]
Message-ID: <20161114153814.GA26664@stefanha-x1.localdomain> (raw)
In-Reply-To: <1478869302-2559-1-git-send-email-famz@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

On Fri, Nov 11, 2016 at 09:01:41PM +0800, Fam Zheng wrote:
> The following changes since commit 6bbcb76301a72dc80c8d29af13d40bb9a759c9c6:
> 
>   MAINTAINERS: Remove obsolete stable branches (2016-11-10 15:29:59 +0000)
> 
> are available in the git repository at:
> 
>   git@github.com:famz/qemu tags/for-upstream
> 
> for you to fetch changes up to d9c05e507f7a6647cd7b106c8784f1f15a0e4f5c:
> 
>   test-uuid: fix leak (2016-11-11 20:53:23 +0800)
> 
> ----------------------------------------------------------------
> 
> This is the memory leak fix for uuid test.
> 
> ----------------------------------------------------------------
> 
> Marc-André Lureau (1):
>   test-uuid: fix leak
> 
>  tests/test-uuid.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> -- 
> 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 --]

      parent reply	other threads:[~2016-11-14 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 13:01 [Qemu-devel] [PULL 0/1] UUID test fix patch for 2.8 Fam Zheng
2016-11-11 13:01 ` [Qemu-devel] [PULL 1/1] test-uuid: fix leak Fam Zheng
2016-11-11 13:18 ` [Qemu-devel] [PULL 0/1] UUID test fix patch for 2.8 Fam Zheng
2016-11-14 15:38 ` 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=20161114153814.GA26664@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=famz@redhat.com \
    --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).