From: Blue Swirl <blauwirbel@gmail.com>
To: Ulrich Hecht <uli@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] warnings in net.c
Date: Wed, 17 Jun 2009 19:23:49 +0300 [thread overview]
Message-ID: <f43fc5580906170923i2eb2fc4euf89d70020ec51a95@mail.gmail.com> (raw)
In-Reply-To: <1245253660-12616-1-git-send-email-uli@suse.de>
On 6/17/09, Ulrich Hecht <uli@suse.de> wrote:
> removes unused slirp code and initializes ret in net_client_init()
Totally bogus, you must be compiling without CONFIG_SLIRP.
next prev parent reply other threads:[~2009-06-17 16:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 15:47 [Qemu-devel] [PATCH] warnings in net.c Ulrich Hecht
2009-06-17 16:06 ` Filip Navara
2009-06-17 16:37 ` [Qemu-devel] " Jan Kiszka
2009-06-18 10:01 ` Ulrich Hecht
2009-06-18 9:56 ` [Qemu-devel] " Ulrich Hecht
2009-06-18 18:31 ` [Qemu-devel] " Jan Kiszka
2009-06-17 16:23 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-03 15:09 [Qemu-devel] [PATCH 0/4] linux-user syscall bugs Ulrich Hecht
2009-07-03 15:09 ` [Qemu-devel] [PATCH 1/4] pipe argument should not be signed Ulrich Hecht
2009-07-03 15:09 ` [Qemu-devel] [PATCH] warnings in net.c Ulrich Hecht
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=f43fc5580906170923i2eb2fc4euf89d70020ec51a95@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=uli@suse.de \
/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).