qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@qumranet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/6] Add "info uuid" command to monitor.
Date: Mon, 25 Aug 2008 12:46:04 +0300	[thread overview]
Message-ID: <20080825094604.GJ6192@minantech.com> (raw)
In-Reply-To: <f43fc5580808241043j16eead7dqc9539201e439d8b6@mail.gmail.com>

On Sun, Aug 24, 2008 at 08:43:41PM +0300, Blue Swirl wrote:
> On 8/24/08, Gleb Natapov <gleb@qumranet.com> wrote:
> > Signed-off-by: Gleb Natapov <gleb@qumranet.com>
> >  ---
> >
> >   monitor.c |   13 +++++++++++++
> >   1 files changed, 13 insertions(+), 0 deletions(-)
> >
> >  diff --git a/monitor.c b/monitor.c
> >  index e71f49e..1e477bb 100644
> >  --- a/monitor.c
> >  +++ b/monitor.c
> >  @@ -253,6 +253,17 @@ static void do_info_name(void)
> >          term_printf("%s\n", qemu_name);
> >   }
> >
> >  +static void do_info_uuid(void)
> >  +{
> >  +    char uuid_str[37];
> >  +    sprintf(uuid_str, UUID_FMT, qemu_uuid[0], qemu_uuid[1], qemu_uuid[2],
> >  +            qemu_uuid[3], qemu_uuid[4], qemu_uuid[5], qemu_uuid[6],
> >  +            qemu_uuid[7], qemu_uuid[8], qemu_uuid[9], qemu_uuid[10],
> >  +            qemu_uuid[11], qemu_uuid[12], qemu_uuid[13], qemu_uuid[14],
> >  +            qemu_uuid[15]);
> >  +    term_printf("%s\n", uuid_str);
> 
> Please use snprintf. Or why not directly term_printf(UUID_FMT "\n",
> qemu_uuid[0] etc.?
Don't know. I've removed redundant sprintf. Thanks.

--
			Gleb.

  reply	other threads:[~2008-08-25  9:46 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-24 11:32 [Qemu-devel] [PATCH 0/6] Add UUID command-line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 1/6] Use IO port for qemu<->guest BIOS communication Gleb Natapov
2008-08-24 17:39   ` Blue Swirl
2008-08-25  9:48     ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 2/6] Add -uuid command line option Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 3/6] Add "info uuid" command to monitor Gleb Natapov
2008-08-24 17:43   ` Blue Swirl
2008-08-25  9:46     ` Gleb Natapov [this message]
2008-08-24 11:33 ` [Qemu-devel] [PATCH 4/6] Use libuuid if available Gleb Natapov
2008-08-24 17:50   ` Blue Swirl
2008-08-25  9:44     ` Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 5/6] Add UUID to BIOS configuration info Gleb Natapov
2008-08-24 11:33 ` [Qemu-devel] [PATCH 6/6] Pass cpu speed into SM BIOS Gleb Natapov
2008-08-24 18:14   ` Blue Swirl
2008-08-25  9:44     ` Gleb Natapov
2008-08-24 12:01 ` [Qemu-devel] [PATCH 0/6] Add UUID command-line option Blue Swirl
2008-08-24 12:24   ` Gleb Natapov
2008-08-24 12:45     ` Blue Swirl
2008-08-24 13:05       ` Gleb Natapov
2008-08-24 13:35         ` Blue Swirl
2008-08-24 14:11           ` Gleb Natapov
2008-08-24 17:17             ` Blue Swirl
2008-08-24 19:23           ` Kevin O'Connor
2008-08-24 13:09       ` Avi Kivity
2008-08-24 13:43         ` Blue Swirl
2008-08-24 13:55           ` Avi Kivity
2008-08-24 16:56             ` Blue Swirl
2008-08-25  9:32               ` Avi Kivity
2008-08-25 14:22                 ` Anthony Liguori
2008-08-24 18:50             ` Kevin O'Connor
2008-08-25  9:29               ` Avi Kivity

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=20080825094604.GJ6192@minantech.com \
    --to=gleb@qumranet.com \
    --cc=qemu-devel@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 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).