From: Gerd Hoffmann <kraxel@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Paul Brook <paul@codesourcery.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH] Sparc32/PPC: convert escc to qdev
Date: Wed, 15 Jul 2009 17:37:24 +0200 [thread overview]
Message-ID: <4A5DF7B4.4010806@redhat.com> (raw)
In-Reply-To: <f43fc5580907150747v34e7a6f1l60677ac035de2003@mail.gmail.com>
On 07/15/09 16:47, Blue Swirl wrote:
>> >> > + qdev_set_prop_int(dev, "frequency", clock);
>>>> > + clock = qdev_get_prop_int(&dev->qdev, "clock", 0);
> I see, thanks. Maybe an attempt to use an undeclared property should
> raise an abort().
Once my qdev property monster patch is finally merged it all will be
there. get_prop() is not needed any more, and set_prop works only for
explicitly defined properties.
cheers,
Gerd
prev parent reply other threads:[~2009-07-15 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 19:32 [Qemu-devel] [PATCH] Sparc32/PPC: convert escc to qdev Blue Swirl
[not found] ` <m3k52c8evv.fsf@neno.mitica>
2009-07-14 18:54 ` [Qemu-devel] " Blue Swirl
2009-07-14 22:03 ` Juan Quintela
2009-07-15 14:47 ` Blue Swirl
2009-07-15 15:37 ` 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=4A5DF7B4.4010806@redhat.com \
--to=kraxel@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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 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).