From: Luiz Capitulino <lcapitulino@redhat.com>
To: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
Cc: avi@redhat.com, qemu-devel@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0/7] QMP: Introduce query-netdev
Date: Mon, 28 Jun 2010 19:01:49 -0300 [thread overview]
Message-ID: <20100628190149.46f9c1f3@redhat.com> (raw)
In-Reply-To: <1277307603-28960-1-git-send-email-miguel.filho@gmail.com>
On Wed, 23 Jun 2010 12:39:56 -0300
Miguel Di Ciurcio Filho <miguel.filho@gmail.com> wrote:
> This series implement the previously discussed QMP command query-netdev.
>
> There is small change in the specification from the last version: when "type" is
> "tap", the attribute "sndbuf" have been removed. "sndbuf" is not available on
> all platforms and most of the tap_set_sndbuf() implementations are stubs.
Apart from the two bugs I found, looks good to me.
My only remaining question is: isn't socket a backend?
prev parent reply other threads:[~2010-06-28 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 15:39 [Qemu-devel] [PATCH 0/7] QMP: Introduce query-netdev Miguel Di Ciurcio Filho
2010-06-23 15:39 ` [Qemu-devel] [PATCH 1/7] QMP: Introduce the documentation for query-netdev and info netdev Miguel Di Ciurcio Filho
2010-06-23 15:39 ` [Qemu-devel] [PATCH 2/7] QObject API: introduce qdict_to_qstring() function Miguel Di Ciurcio Filho
2010-06-23 15:39 ` [Qemu-devel] [PATCH 3/7] net: Introduce VLANClientState->info_dict Miguel Di Ciurcio Filho
2010-06-28 21:59 ` [Qemu-devel] " Luiz Capitulino
2010-06-23 15:40 ` [Qemu-devel] [PATCH 4/7] net: tap/tap-win32: introduce info_dict Miguel Di Ciurcio Filho
2010-06-23 15:40 ` [Qemu-devel] [PATCH 5/7] net: vde: " Miguel Di Ciurcio Filho
2010-06-23 15:40 ` [Qemu-devel] [PATCH 6/7] net: slirp: " Miguel Di Ciurcio Filho
2010-06-23 15:40 ` [Qemu-devel] [PATCH 7/7] monitor/net: introduce 'info netdev' with QMP support Miguel Di Ciurcio Filho
2010-06-28 22:00 ` [Qemu-devel] " Luiz Capitulino
2010-06-28 22:01 ` Luiz Capitulino [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=20100628190149.46f9c1f3@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=miguel.filho@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.