From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] inconsistency between device traversal in qdev and legacy
Date: Thu, 09 Jun 2011 16:12:14 +0200 [thread overview]
Message-ID: <4DF0D4BE.8090008@redhat.com> (raw)
In-Reply-To: <m37h8v85r7.fsf@blackfin.pond.sub.org>
Hi,
>> Gave up after resending it one or two times, the forgot about it,
>> wasn't *that* important to me.
>
> Still got a pointer to the patch?
Not in my git tree any more. Google found me this instead:
http://permalink.gmane.org/gmane.comp.emulators.qemu/74360
Looks like I'm not the only one who tried ...
cheers,
Gerd
next prev parent reply other threads:[~2011-06-09 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 15:07 [Qemu-devel] inconsistency between device traversal in qdev and legacy Peter Maydell
2011-06-08 17:00 ` Gerd Hoffmann
2011-06-08 17:37 ` Andreas Färber
2011-06-08 17:39 ` Peter Maydell
2011-06-08 18:19 ` Rob Landley
2011-06-08 19:06 ` Andreas Färber
2011-06-09 13:59 ` Markus Armbruster
2011-06-09 14:12 ` Gerd Hoffmann [this message]
2011-06-09 14:32 ` Peter Maydell
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=4DF0D4BE.8090008@redhat.com \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=peter.maydell@linaro.org \
--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).