qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Hani Benhabiles <kroosec@gmail.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/4] monitor: Add device_del id argument completion.
Date: Tue, 11 Feb 2014 13:35:44 -0500	[thread overview]
Message-ID: <20140211133544.00238b21@redhat.com> (raw)
In-Reply-To: <1391725813-29514-2-git-send-email-kroosec@gmail.com>

On Thu,  6 Feb 2014 23:30:10 +0100
Hani Benhabiles <kroosec@gmail.com> wrote:

> ---
>  monitor.c | 23 +++++++++++++++++++++++
>  1 file changed, 23 insertions(+)

Your S-o-B is missing in all patches. Can reply to them adding it?

> 
> diff --git a/monitor.c b/monitor.c
> index b1ea262..f8c4cae 100644
> --- a/monitor.c
> +++ b/monitor.c
> @@ -4254,6 +4254,25 @@ static const char *next_arg_type(const char *typestr)
>      return (p != NULL ? ++p : typestr);
>  }
>  
> +static void device_del_completion(ReadLineState *rs, BusState *bus,
> +                                  const char *str, size_t len)
> +{
> +    BusChild *kid;
> +
> +    QTAILQ_FOREACH(kid, &bus->children, sibling) {
> +        DeviceState *dev = kid->child;
> +        BusState *dev_child;
> +
> +        if (dev->id && !strncmp(str, dev->id, len)) {
> +            readline_add_completion(rs, dev->id);
> +        }
> +
> +        QLIST_FOREACH(dev_child, &dev->child_bus, sibling) {
> +            device_del_completion(rs, dev_child, str, len);
> +        }
> +    }
> +}
> +
>  static void monitor_find_completion_by_table(Monitor *mon,
>                                               const mon_cmd_t *cmd_table,
>                                               char **args,
> @@ -4330,6 +4349,10 @@ static void monitor_find_completion_by_table(Monitor *mon,
>              } else if (!strcmp(cmd->name, "help|?")) {
>                  monitor_find_completion_by_table(mon, cmd_table,
>                                                   &args[1], nb_args - 1);
> +            } else if (!strcmp(cmd->name, "device_del") && nb_args == 2) {
> +                size_t len = strlen(str);
> +                readline_set_completion_index(mon->rs, len);
> +                device_del_completion(mon->rs, sysbus_get_default(), str, len);
>              }
>              break;
>          default:

  reply	other threads:[~2014-02-11 18:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 22:30 [Qemu-devel] [PATCH 0/4] monitor: Add argument completion for multiple commands Hani Benhabiles
2014-02-06 22:30 ` [Qemu-devel] [PATCH 1/4] monitor: Add device_del id argument completion Hani Benhabiles
2014-02-11 18:35   ` Luiz Capitulino [this message]
2014-02-06 22:30 ` [Qemu-devel] [PATCH 2/4] monitor: Add device_add device " Hani Benhabiles
2014-02-06 22:30 ` [Qemu-devel] [PATCH 3/4] monitor: Add object_del id " Hani Benhabiles
2014-02-06 22:30 ` [Qemu-devel] [PATCH 4/4] monitor: Add object_add class " Hani Benhabiles
2014-02-11 18:38   ` Luiz Capitulino
2014-02-11 22:14     ` Hani Benhabiles
2014-02-11 18:39 ` [Qemu-devel] [PATCH 0/4] monitor: Add argument completion for multiple commands Luiz Capitulino
2014-02-11 22:10   ` Hani Benhabiles

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=20140211133544.00238b21@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=kroosec@gmail.com \
    --cc=pbonzini@redhat.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).