From: Mark McLoughlin <markmc@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] Clean up error handling in net.c
Date: Wed, 30 Sep 2009 11:29:44 +0100 [thread overview]
Message-ID: <1254306584.3105.22.camel@blaa> (raw)
In-Reply-To: <cover.1254164473.git.armbru@redhat.com>
On Mon, 2009-09-28 at 21:11 +0200, Markus Armbruster wrote:
> Caveat: I'm not familiar with slirp, and I'm not sure 1/3 is the right
> thing to do.
>
> Markus Armbruster (3):
> Make net_client_init() consume slirp_configs even on error
> Don't exit() in config_error()
> Drop config_error(), use qemu_error() instead
The series looks good to me
Since it conflicts significantly with my conversion of -net to QemuOpts,
I've pulled them into my tree (modulo the spurious USB change) and
re-based:
http://git.et.redhat.com/?p=qemu-net.git
Hope you agree that makes sense
Thanks,
Mark.
prev parent reply other threads:[~2009-09-30 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 19:11 [Qemu-devel] [PATCH 0/3] Clean up error handling in net.c Markus Armbruster
2009-09-28 19:41 ` Luiz Capitulino
2009-09-29 12:32 ` Markus Armbruster
2009-09-30 10:29 ` Mark McLoughlin [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=1254306584.3105.22.camel@blaa \
--to=markmc@redhat.com \
--cc=armbru@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).