xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v2 0/4] gcov: more cleanup
Date: Wed, 7 Sep 2016 07:35:28 +0100	[thread overview]
Message-ID: <20160907063528.GB19584@citrix.com> (raw)
In-Reply-To: <1473165667-25707-1-git-send-email-wei.liu2@citrix.com>

On Tue, Sep 06, 2016 at 01:41:03PM +0100, Wei Liu wrote:
> Wei Liu (4):
>   xen: indicate gcov in log messages
>   gcov: collect more sections to constructor list
>   xen: replace TEST_COVERAGE with CONFIG_GCOV
>   xen: make clear gcov support limitation in Kconfig
> 

I believe this series has got sufficient reviews / acks and all
questions answered (with help from Andrew), so I pushed it just now.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-09-07  6:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06 12:41 [PATCH v2 0/4] gcov: more cleanup Wei Liu
2016-09-06 12:41 ` [PATCH v2 1/4] xen: indicate gcov in log messages Wei Liu
2016-09-06 12:47   ` Andrew Cooper
2016-09-06 13:34     ` Jan Beulich
2016-09-06 14:06       ` Wei Liu
2016-09-06 14:16         ` Jan Beulich
2016-09-06 14:17         ` Andrew Cooper
2016-09-06 22:06   ` Stefano Stabellini
2016-09-06 12:41 ` [PATCH v2 2/4] gcov: collect more sections to constructor list Wei Liu
2016-09-06 13:35   ` Jan Beulich
2016-09-06 12:41 ` [PATCH v2 3/4] xen: replace TEST_COVERAGE with CONFIG_GCOV Wei Liu
2016-09-06 12:41 ` [PATCH v2 4/4] xen: make clear gcov support limitation in Kconfig Wei Liu
2016-09-06 13:37   ` Jan Beulich
2016-09-06 13:42     ` Andrew Cooper
2016-09-07  6:35 ` Wei Liu [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=20160907063528.GB19584@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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).