qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Andreas Färber" <andreas.faerber@web.de>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] inconsistency between device traversal in qdev and legacy
Date: Wed, 08 Jun 2011 13:19:32 -0500	[thread overview]
Message-ID: <4DEFBD34.1050507@landley.net> (raw)
In-Reply-To: <BANLkTi=BT=mWypNvmoSOPV_W1Pn8T-eEwg@mail.gmail.com>

On 06/08/2011 12:39 PM, Peter Maydell wrote:
> On 8 June 2011 18:37, Andreas Färber <andreas.faerber@web.de> wrote:
>> From Peter's description I believe this could be the root cause of Rob's
>> reversed -net /dev/ethX devices as well? That supposedly broke with 0.14. So
>> for setups earlier than 0.14 reversing would be a bugfix, but if people
>> adapted to 0.14 behavior changing it back would break things. Difficult
>> call.
> 
> OTOH if not many people complained about the 0.13->0.14 transition then
> presumably not very many will complain if we put it back? :-)
> 
> -- PMM

I suspect most people emulating boards only feed one interface to the
thing, so it probably doesn't come up much.

Either way, I have a workaround now, but consistency would be nice.

Rob

  reply	other threads:[~2011-06-08 18:19 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 [this message]
2011-06-08 19:06       ` Andreas Färber
2011-06-09 13:59   ` Markus Armbruster
2011-06-09 14:12     ` Gerd Hoffmann
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=4DEFBD34.1050507@landley.net \
    --to=rob@landley.net \
    --cc=andreas.faerber@web.de \
    --cc=armbru@redhat.com \
    --cc=kraxel@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).