All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2 of 5] tools/xc: document printf calls in xc_restore
Date: Tue, 12 Mar 2013 17:47:10 +0100	[thread overview]
Message-ID: <20130312164710.GA26446@aepfle.de> (raw)
In-Reply-To: <1363106179.32410.45.camel@zakaz.uk.xensource.com>

On Tue, Mar 12, Ian Campbell wrote:

> On Wed, 2013-03-06 at 16:48 +0000, Olaf Hering wrote:
> > # HG changeset patch
> > # User Olaf Hering <olaf@aepfle.de>
> > # Date 1362584522 -3600
> > # Node ID 49b90990442aca9523acbf889cbb517ea44d20b4
> > # Parent  e5ae0e680b5c64d7808bb6a68ea47ef1bbf68a51
> > tools/xc: document printf calls in xc_restore
> > 
> > Signed-off-by: Olaf Hering <olaf@aepfle.de>
> > 
> > diff -r e5ae0e680b5c -r 49b90990442a tools/xcutils/xc_restore.c
> > --- a/tools/xcutils/xc_restore.c
> > +++ b/tools/xcutils/xc_restore.c
> > @@ -56,6 +56,7 @@ main(int argc, char **argv)
> >  
> >      if ( ret == 0 )
> >      {
> > +        /* xend expects this output, part of protocol */
> 
> xc_restore is effectively part of xend (just factored into its own
> process), no one else uses this stuff.
> 
> What I guess I'm saying is that we can take everything which this file
> does as being desired by xend...

The purpose is more to not convert them to DPRINTF or something, like I
did it once until I realized that these printf calls should stay as is.

Olaf

  reply	other threads:[~2013-03-12 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 16:48 [PATCH 0 of 5] set migrate constraints from cmdline, better xend.log logging Olaf Hering
2013-03-06 16:48 ` [PATCH 1 of 5] tools/xc: print messages from xc_save with xc_report Olaf Hering
2013-03-06 16:48 ` [PATCH 2 of 5] tools/xc: document printf calls in xc_restore Olaf Hering
2013-03-12 16:36   ` Ian Campbell
2013-03-12 16:47     ` Olaf Hering [this message]
2013-03-12 16:50       ` Ian Campbell
2013-03-12 16:58         ` Olaf Hering
2013-03-06 16:48 ` [PATCH 3 of 5] tools/xc: rework xc_save.c:switch_qemu_logdirty Olaf Hering
2013-03-06 18:13   ` Olaf Hering
2013-03-06 16:48 ` [PATCH 4 of 5] tools: set migration constraints from cmdline Olaf Hering
2013-03-12 16:48   ` Ian Campbell
2013-03-12 17:06     ` Olaf Hering
2013-03-06 16:48 ` [PATCH 5 of 5] tools: add xm migrate --log_progress option Olaf Hering
2013-03-12 16:36 ` [PATCH 0 of 5] set migrate constraints from cmdline, better xend.log logging Ian Campbell

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=20130312164710.GA26446@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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.