All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
	qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC 02/13] qdev: split up header so it can be used in cpu.h
Date: Tue, 16 Oct 2012 02:01:15 +0200	[thread overview]
Message-ID: <507CA3CB.3050705@suse.de> (raw)
In-Reply-To: <1349378133-25644-3-git-send-email-ehabkost@redhat.com>

Am 04.10.2012 21:15, schrieb Eduardo Habkost:
> From: Anthony Liguori <aliguori@us.ibm.com>
> 
> Header file dependency is a frickin' nightmare right now.  cpu.h tends to get
> included in our 'include everything' header files but qdev also needs to include
> those headers mainly for qdev-properties since it knows about CharDriverState
> and friends.
> 
> We can solve this for now by splitting out qdev.h along the same lines that we
> previously split the C file.  Then cpu.h just needs to include qdev-core.h
> 
> [ehabkost: re-add DEFINE_PROP_PCI_HOST_DEVADDR, that was removed on the
>  original patch (by mistake, I guess)]
> [ehabkost: kill qdev_prop_set_vlan() declaration]
> 
> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>

Generally I am still in favor of doing such a per-topic file split, in
whatever way exactly we proceed with CPU-as-a-device.

If this is supposed to go through my CPU queue then I would prefer to
move the [ehabkost: ...] lines chronologically between the Sobs fwiw.

What I would insist on is mentioning both new file names in the commit
message (qdev-core.h and qdev-properties.h iiuc) since the +++ stats are
ambiguous.

I spotted the following textual discrepancy:

> diff --git a/hw/qdev-core.h b/hw/qdev-core.h
> new file mode 100644
> index 0000000..ca205fc
> --- /dev/null
> +++ b/hw/qdev-core.h
[...]
> +/*
> + * This callback is used to create Open Firmware device path in accordance with
> + * OF spec http://forthworks.com/standards/of1275.pdf. Indicidual bus bindings
> + * can be found here http://playground.sun.com/1275/bindings/.
> + */
[...]
> diff --git a/hw/qdev.h b/hw/qdev.h
> index d699194..365b8d6 100644
> --- a/hw/qdev.h
> +++ b/hw/qdev.h
[...]
> -    /*
> -     * This callback is used to create Open Firmware device path in accordance
> -     * with OF spec http://forthworks.com/standards/of1275.pdf. Individual bus
> -     * bindings can be found at http://playground.sun.com/1275/bindings/.
> -     */
[snip]

"Individual" became "Indicidual" and the comment seems misplaced, which
makes myself ask whether this split was not done safely via copy&paste?

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-10-16  0:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 19:15 [Qemu-devel] [RFC v2 00/13] include qdev core in *-user, make CPU child of DeviceState Eduardo Habkost
2012-10-04 19:15 ` [Qemu-trivial] [RFC 01/13] qdev: kill bogus comment Eduardo Habkost
2012-10-04 19:15   ` [Qemu-devel] " Eduardo Habkost
2012-10-05 13:49   ` [Qemu-trivial] " Stefan Hajnoczi
2012-10-05 13:49     ` [Qemu-devel] " Stefan Hajnoczi
2012-10-04 19:15 ` [Qemu-devel] [RFC 02/13] qdev: split up header so it can be used in cpu.h Eduardo Habkost
2012-10-16  0:01   ` Andreas Färber [this message]
2012-10-04 19:15 ` [Qemu-devel] [RFC 03/13] qapi-types.h doesn't really need to include qemu-common.h Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 04/13] qdev: separate core from the code used only by qemu-system-* Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 05/13] qdev: rename qdev.c to qdev-core.c Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 06/13] qdev-core: isolate vmstate handling into separate functions Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 07/13] qdev: move vmstate handling to qdev-system.c Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 08/13] qdev-core: isolate reset register/unregister code Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 09/13] qdev: move reset register/unregister code to qdev-system.c Eduardo Habkost
2012-10-16 14:13   ` Anthony Liguori
2012-10-04 19:15 ` [Qemu-devel] [RFC 10/13] move qemu_irq typedef out of cpu-common.h Eduardo Habkost
2012-10-04 20:20   ` Peter Maydell
2012-10-04 19:15 ` [Qemu-devel] [RFC 11/13] qdev: use full qdev.h include path on qdev*.c Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 12/13] include core qdev code into *-user, too Eduardo Habkost
2012-10-04 19:15 ` [Qemu-devel] [RFC 13/13] make CPU a child of DeviceState Eduardo Habkost
2012-10-09 14:43   ` Peter Crosthwaite

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=507CA3CB.3050705@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@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 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.