From: Jan Kiszka <jan.kiszka@web.de>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH] slirp: Fix guestfwd for incoming data
Date: Wed, 22 Jul 2009 20:56:05 +0200 [thread overview]
Message-ID: <4A6760C5.7090609@web.de> (raw)
In-Reply-To: <20090722172859.GC24302@amd.home.annexia.org>
[-- Attachment #1: Type: text/plain, Size: 515 bytes --]
Richard W.M. Jones wrote:
> On Wed, Jul 22, 2009 at 05:03:52PM +0200, Jan Kiszka wrote:
>> Unless a virtual server address was explicitly defined (which is
>> impossible with the legacy -net channel format), guestfwd did not
>> properly forwarded host->guest packets. This patch fixes it.
>
> Yes, I've confirmed this works.
>
> PLEASE apply this patch!
>
> Thanks, Rich.
>
Great.
Just leaves us with that syntax wreckage. Will try to look into -char
support like Anthony suggested.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-07-22 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 15:03 [Qemu-devel] [PATCH] slirp: Fix guestfwd for incoming data Jan Kiszka
2009-07-22 17:28 ` [Qemu-devel] " Richard W.M. Jones
2009-07-22 18:56 ` Jan Kiszka [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=4A6760C5.7090609@web.de \
--to=jan.kiszka@web.de \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).