From: Stefan Hajnoczi <stefanha@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2.4] socket: pass correct size in net_socket_send()
Date: Thu, 9 Jul 2015 10:41:24 +0100 [thread overview]
Message-ID: <20150709094124.GA23667@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1436259656-24263-1-git-send-email-jasowang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
On Tue, Jul 07, 2015 at 05:00:56PM +0800, Jason Wang wrote:
> We should pass the size of packet instead of the remaining to
> qemu_send_packet_async().
>
> Fixes: 6e99c631f116221d169ea53953d91b8aa74d297a
> ("net/socket: Drop net_socket_can_send")
>
> Signed-off-by: Jason Wang <jasowang@redhat.com>
> ---
> net/socket.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, applied to my net tree:
https://github.com/stefanha/qemu/commits/net
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-07-09 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 9:00 [Qemu-devel] [PATCH 2.4] socket: pass correct size in net_socket_send() Jason Wang
2015-07-07 9:09 ` Fam Zheng
2015-07-09 9:41 ` Stefan Hajnoczi [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=20150709094124.GA23667@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=jasowang@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).