From: "Michael S. Tsirkin" <mst@redhat.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: pbonzini@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v2 1/3] hw: import bitmap operations in qdev-core header
Date: Mon, 29 Jul 2013 10:42:15 +0300 [thread overview]
Message-ID: <20130729074215.GD2308@redhat.com> (raw)
In-Reply-To: <1375081655-28541-2-git-send-email-marcel.a@redhat.com>
On Mon, Jul 29, 2013 at 10:07:33AM +0300, Marcel Apfelbaum wrote:
> Made small tweaks in code to prevent compilation issues
> when importing qemu/bitmap.h in qdev-core
>
> Signed-off-by: Marcel Apfelbaum <marcel.a@redhat.com>
> ---
> hw/core/qdev-properties.c | 4 ++--
> hw/net/eepro100.c | 1 -
> include/hw/qdev-core.h | 1 +
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/hw/core/qdev-properties.c b/hw/core/qdev-properties.c
> index 3a324fb..01b27eb 100644
> --- a/hw/core/qdev-properties.c
> +++ b/hw/core/qdev-properties.c
> @@ -91,7 +91,7 @@ static void get_bit(Object *obj, Visitor *v, void *opaque,
> visit_type_bool(v, &value, name, errp);
> }
>
> -static void set_bit(Object *obj, Visitor *v, void *opaque,
> +static void prop_set_bit(Object *obj, Visitor *v, void *opaque,
> const char *name, Error **errp)
> {
> DeviceState *dev = DEVICE(obj);
> @@ -117,7 +117,7 @@ PropertyInfo qdev_prop_bit = {
> .legacy_name = "on/off",
> .print = print_bit,
> .get = get_bit,
> - .set = set_bit,
> + .set = prop_set_bit,
> };
>
> /* --- bool --- */
Other code uses qdev_prop prefix, which makes sense I think.
Let's also update get_bit and print_bit, keep it consistent.
> diff --git a/hw/net/eepro100.c b/hw/net/eepro100.c
> index e0befb2..3dc4937 100644
> --- a/hw/net/eepro100.c
> +++ b/hw/net/eepro100.c
> @@ -105,7 +105,6 @@
> #define PCI_IO_SIZE 64
> #define PCI_FLASH_SIZE (128 * KiB)
>
> -#define BIT(n) (1 << (n))
> #define BITS(n, m) (((0xffffffffU << (31 - n)) >> (31 - n + m)) << m)
>
> /* The SCB accepts the following controls for the Tx and Rx units: */
Please #include "qemu/bitops.h" - don't rely on other headers
pulling it in.
> diff --git a/include/hw/qdev-core.h b/include/hw/qdev-core.h
> index 7fbffcb..e8b89b1 100644
> --- a/include/hw/qdev-core.h
> +++ b/include/hw/qdev-core.h
> @@ -4,6 +4,7 @@
> #include "qemu/queue.h"
> #include "qemu/option.h"
> #include "qemu/typedefs.h"
> +#include "qemu/bitmap.h"
> #include "qom/object.h"
> #include "hw/irq.h"
> #include "qapi/error.h"
> --
> 1.8.3.1
next prev parent reply other threads:[~2013-07-29 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 7:07 [Qemu-devel] [PATCH v2 0/3] qemu-help: improve -device command line help Marcel Apfelbaum
2013-07-29 7:07 ` [Qemu-devel] [PATCH v2 1/3] hw: import bitmap operations in qdev-core header Marcel Apfelbaum
2013-07-29 7:42 ` Michael S. Tsirkin [this message]
2013-07-29 8:01 ` Marcel Apfelbaum
2013-07-29 7:07 ` [Qemu-devel] [PATCH v2 2/3] qemu-help: Sort devices by logical functionality Marcel Apfelbaum
2013-07-29 8:04 ` Michael S. Tsirkin
2013-07-29 8:14 ` Marcel Apfelbaum
2013-07-29 8:20 ` Michael S. Tsirkin
2013-07-29 9:09 ` Marcel Apfelbaum
2013-07-29 9:22 ` Michael S. Tsirkin
2013-07-29 9:26 ` Marcel Apfelbaum
2013-07-29 7:07 ` [Qemu-devel] [PATCH v2 3/3] devices: Associate devices to their logical category Marcel Apfelbaum
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=20130729074215.GD2308@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=marcel.a@redhat.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).