From: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [RFC] New Monitor command: 'info netdevices'
Date: Fri, 14 May 2010 09:38:58 -0300 [thread overview]
Message-ID: <AANLkTikpTihEMCDrCQCLbcwKuuA0WNuCeeqs6T7vVMQH@mail.gmail.com> (raw)
In-Reply-To: <m3aas2ke8g.fsf@blackfin.pond.sub.org>
On Fri, May 14, 2010 at 6:46 AM, Markus Armbruster <armbru@redhat.com> wrote:
>
> There's also
>
> 3. Convert it anyway. Clean up the mess. Change the output.
>
I agree.
It seams to me that no one is concerned with any Monitor output change
with this particular command.
Plus, no one have shown any concerns about the problems I've found in
net/socket.c reported previously either.
next prev parent reply other threads:[~2010-05-14 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 14:18 [Qemu-devel] [RFC] New Monitor command: 'info netdevices' Luiz Capitulino
2010-05-14 9:46 ` Markus Armbruster
2010-05-14 12:38 ` Miguel Di Ciurcio Filho [this message]
2010-05-14 14:07 ` Luiz Capitulino
2010-05-14 13:30 ` [Qemu-devel] " Anthony Liguori
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=AANLkTikpTihEMCDrCQCLbcwKuuA0WNuCeeqs6T7vVMQH@mail.gmail.com \
--to=miguel.filho@gmail.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@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 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).