qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: scottwood@freescale.com, qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 1/3] pseries: Clean up hcall_dprintf() debugging messages
Date: Wed, 04 Apr 2012 17:23:30 +0200	[thread overview]
Message-ID: <4F7C6772.7060101@suse.de> (raw)
In-Reply-To: <1332970787-14598-1-git-send-email-david@gibson.dropbear.id.au>

Am 28.03.2012 23:39, schrieb David Gibson:
> The pseries machine code has a number of debug messages for debugging PAPR
> hypercalls, dependent on DEBUG_SPAPR_HCALLS.  This patch cleans these
> messages up a bit, by adding __func__ to the hcall_dprintf() macro and
> simplifying up a number of the individual messages accordingly.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> 
> Conflicts:
> 
> 	hw/spapr_vio.c
> ---

Thanks, that cleanup went beyond what I expected for what-is-now-2/3.

Applied to ppc-next:
http://repo.or.cz/w/qemu/agraf.git/shortlog/refs/heads/ppc-next

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

      parent reply	other threads:[~2012-04-04 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 21:39 [Qemu-devel] [PATCH 1/3] pseries: Clean up hcall_dprintf() debugging messages David Gibson
2012-03-28 21:39 ` [Qemu-devel] [PATCH 2/3] pseries: Fix bug with reset of VIO CRQs David Gibson
2012-04-04 16:13   ` Andreas Färber
2012-04-05  1:12     ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-04-05  2:30     ` David Gibson
2012-03-28 21:39 ` [Qemu-devel] [PATCH 3/3] pseries: Implement RTAS system-reboot call David Gibson
2012-04-04 15:23 ` Andreas Färber [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=4F7C6772.7060101@suse.de \
    --to=afaerber@suse.de \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=scottwood@freescale.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).