From: Gerd Hoffmann <kraxel@redhat.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] qdev: kill DeviceState->nd, use properties instead.
Date: Fri, 29 May 2009 15:17:15 +0200 [thread overview]
Message-ID: <4A1FE05B.30800@redhat.com> (raw)
In-Reply-To: <200905291310.09405.paul@codesourcery.com>
On 05/29/09 14:10, Paul Brook wrote:
>> kill DeviceState->nd, use properties instead.
>
> I'm not sure this is the right solution. Before changing this I think we need
> to figure out how we want to link devices to the host network configuration.
Sure, when we replace the vlans with something else the vlan property
wouldn't make sense any more (guess this is the discussion you are
referring to). We can drop it once we have a replacement for the
current model. Not (yet) having a replacement shouldn't stop us from
putting qdev into use though.
cheers,
Gerd
prev parent reply other threads:[~2009-05-29 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 22:44 [Qemu-devel] [PATCH 1/2] qdev: add string and binary properties Gerd Hoffmann
2009-05-28 22:44 ` [Qemu-devel] [PATCH 2/2] qdev: kill DeviceState->nd, use properties instead Gerd Hoffmann
2009-05-29 12:10 ` Paul Brook
2009-05-29 13:17 ` Gerd Hoffmann [this message]
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=4A1FE05B.30800@redhat.com \
--to=kraxel@redhat.com \
--cc=paul@codesourcery.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).