All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
	armbru@redhat.com, qemu-ppc <qemu-ppc@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	g@voom.redhat.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/3] prep: do not use CPU_LOG_IOPORT, convert to tracepoints
Date: Fri, 23 Oct 2015 11:37:21 +0200	[thread overview]
Message-ID: <5629FFD1.5040009@web.de> (raw)
In-Reply-To: <20151023013820.GB27149@voom.redhat.com>

Am 23.10.2015 um 03:38 schrieb David Gibson:
> On Fri, Oct 16, 2015 at 03:16:11PM +0200, Paolo Bonzini wrote:
>> These messages are disabled by default; a perfect usecase for tracepoints.
>> Convert them over.
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> 
> Looks good to me.  Applied to ppc-next.

Would've been nice to ask first, but

Acked-by: Andreas Färber <andreas.faerber@web.de>

I do have some PReP refactorings for a 2.4 issue from Markus that I
would like to get into 2.5, so please submit your ppc queue early.

Thanks,
Andreas

  parent reply	other threads:[~2015-10-23  9:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 13:16 [Qemu-devel] [PATCH 0/3] qemu-log: remove -d ioport Paolo Bonzini
2015-10-16 13:16 ` [Qemu-devel] [PATCH 1/3] prep: do not use CPU_LOG_IOPORT, convert to tracepoints Paolo Bonzini
2015-10-23  1:38   ` [Qemu-devel] [Qemu-ppc] " David Gibson
2015-10-23  7:30     ` Paolo Bonzini
2015-10-23  9:37     ` Andreas Färber [this message]
2015-10-16 13:16 ` [Qemu-devel] [PATCH 2/3] ioport: do not use CPU_LOG_IOPORT, expand tracepoints Paolo Bonzini
2015-10-16 13:16 ` [Qemu-devel] [PATCH 3/3] qemu-log: remove -d ioport Paolo Bonzini

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=5629FFD1.5040009@web.de \
    --to=andreas.faerber@web.de \
    --cc=armbru@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=g@voom.redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.