From: Stefan Hajnoczi <stefanha@redhat.com>
To: Mike Day <ncmike@ncultra.org>
Cc: kwolf@redhat.com, Jeff Cody <jcody@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-img: sort block formats in help message
Date: Mon, 5 May 2014 15:42:00 +0200 [thread overview]
Message-ID: <20140505134200.GI16173@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1399036275-9219-1-git-send-email-ncmike@ncultra.org>
On Fri, May 02, 2014 at 09:11:15AM -0400, Mike Day wrote:
> The help message for qemu-img lists the supported block formats, of
> which there are 27 as of version 2.0.50. The formats are printed in
> the order of their driver's position in a linked list, which appears
> random. This patch prints the formats in sorted order, making it
> easier to read and to find a specific format in the list.
Looks useful, thanks!
> Signed-off-by: Mike Day <ncmike@ncultra.org>
> ---
This patch is whitespace-damaged so git-am(1) refuses to apply it.
Please use git-send-email(1) to send patches so that the right format is
used.
$ git am
Applying: qemu-img: sort block formats in help message
fatal: unrecognized input
> qemu-img.c | 33 ++++++++++++++++++++++++++++++++-
> 1 file changed, 32 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 96f4463..d8b7ef4 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -32,6 +32,7 @@
> #include "block/block_int.h"
> #include "block/qapi.h"
> #include <getopt.h>
> +#include <glib.h>
>
> #define QEMU_IMG_VERSION "qemu-img version " QEMU_VERSION \
> ", Copyright (c) 2004-2008 Fabrice Bellard\n"
> @@ -60,6 +61,32 @@ static void format_print(void *opaque, const char *name)
> printf(" %s", name);
> }
>
> +static gint compare_data(gconstpointer a, gconstpointer b, gpointer user)
> +{
> + return g_strcmp0((const char *)a, (const char *)b);
> +}
> +
> +static void GFunc_print_format(gpointer data, gpointer user)
QEMU coding style is lowercase function and variable names. The
scripts/checkpatch.pl script should identify coding style violations,
please run it.
> +{
> + format_print(user, data);
> +}
format_print() isn't called anywhere else, please inline it here since
we no longer need it as its own function.
> +
> +static GSequence *init_sequence(void)
> +{
> + return g_sequence_new(NULL);
> +}
Any reason to hide g_sequence_new(NULL) in it's own helper function?
> +
> +static void add_format_to_seq(void *opaque, const char *fmt_name)
> +{
> + GSequence *seq = (GSequence *)opaque;
> +
> + if (!g_sequence_lookup(seq, (gpointer)fmt_name,
> + compare_data, NULL)) {
> + g_sequence_insert_sorted(seq, (gpointer)fmt_name,
> + compare_data, NULL);
> + }
The type casts in this patch aren't necessary. In C void* casts to and
from any type without an explicit cast. Only C++ demands explicit
casts of void*.
next prev parent reply other threads:[~2014-05-05 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 13:11 [Qemu-devel] [PATCH] qemu-img: sort block formats in help message Mike Day
2014-05-05 13:42 ` Stefan Hajnoczi [this message]
2014-05-05 16:02 ` Mike Day
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 16:07 Mike Day
2014-05-13 17:48 ` Markus Armbruster
2014-05-14 7:50 ` Kevin Wolf
2014-05-14 8:09 ` Fam Zheng
2014-05-14 13:02 ` Stefan Hajnoczi
2014-05-14 13:28 ` Mike Day
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=20140505134200.GI16173@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=ncmike@ncultra.org \
--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).