All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] util: Emancipate id_wellformed() from QemuOpts
Date: Tue, 30 Sep 2014 09:30:37 -0600	[thread overview]
Message-ID: <542ACC9D.8020502@redhat.com> (raw)
In-Reply-To: <1412078370-3555-1-git-send-email-armbru@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]

On 09/30/2014 05:59 AM, Markus Armbruster wrote:
> IDs have long spread beyond QemuOpts: not everything with an ID
> necessarily goes through QemuOpts.  Commit 9aebf3b is about such a
> case: block layer names are meant to be well-formed IDs, but some of
> them don't go through QemuOpts, and thus weren't checked.  The commit
> fixed that the straightforward way: rename the internal QemuOpts
> helper id_wellformed() to qemu_opts_id_wellformed() and give it
> external linkage.
> 
> Instead of using it directly in block.c, the commit adds wrapper
> bdrv_is_valid_name(), probably to hide the connection to QemuOpts.
> 
> Go one logical step further: emancipate IDs from QemuOpts.  Rename the
> function back to id_wellformed(), and put it in another file.  While
> there, clean up its value to bool.  Peel off the bdrv_is_valid_name()
> wrapper.
> ---
>  block.c               |  9 ++-------
>  include/qemu-common.h |  3 +++
>  include/qemu/option.h |  1 -
>  util/Makefile.objs    |  1 +
>  util/id.c             | 28 ++++++++++++++++++++++++++++
>  util/qemu-option.c    | 17 +----------------
>  6 files changed, 35 insertions(+), 24 deletions(-)
>  create mode 100644 util/id.c

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]

  reply	other threads:[~2014-09-30 15:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 11:59 [Qemu-devel] [PATCH] util: Emancipate id_wellformed() from QemuOpts Markus Armbruster
2014-09-30 15:30 ` Eric Blake [this message]
2014-10-01 12:33 ` [Qemu-devel] IDs in QOM (was: [PATCH] util: Emancipate id_wellformed() from QemuOpts) Markus Armbruster
2014-10-02 13:21   ` Stefan Hajnoczi
2014-10-02 13:26     ` [Qemu-devel] IDs in QOM Andreas Färber
2014-10-02 14:10       ` Stefan Hajnoczi
2014-10-02 14:21       ` Markus Armbruster
2014-10-02 14:28         ` Andreas Färber
2014-10-02 14:59           ` Markus Armbruster
2014-10-02 17:41             ` Paolo Bonzini
2014-10-07  8:01               ` Markus Armbruster
2014-10-07 10:03                 ` Paolo Bonzini
2014-10-07 12:16                   ` Markus Armbruster
2014-10-07 15:14                     ` Paolo Bonzini
2014-10-07 18:39                       ` Markus Armbruster
2014-10-07 18:42                         ` Paolo Bonzini
2014-10-07 18:41                       ` Kevin Wolf
2014-10-07 18:45                         ` Paolo Bonzini
2014-10-02 13:18 ` [Qemu-devel] [PATCH] util: Emancipate id_wellformed() from QemuOpts Stefan Hajnoczi
2014-10-02 13:42   ` Markus Armbruster
2014-10-02 14:11     ` Stefan Hajnoczi
2014-10-03  8:46 ` Stefan Hajnoczi

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=542ACC9D.8020502@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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 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.