Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Avi Kivity <akivity@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] net: re-instate some lost vnet_hdr code
Date: Wed, 08 Jul 2009 13:20:44 +0300	[thread overview]
Message-ID: <4A5472FC.1080302@redhat.com> (raw)
In-Reply-To: <1247042858.3270.40.camel@blaa>

On 07/08/2009 11:47 AM, Mark McLoughlin wrote:
> Merge commit 211eb5f301 lost the code we had in tap_send_packet() to
> handle the case of the tapfd having IF_VNET_HDR enabled, but the
> NIC code not having support for virtio_net_hdr. In this case, we just
> strip off the header before passing it to the NIC.
>
> Fixes:
>
>    http://sourceforge.net/tracker/?func=detail&atid=893831&aid=2817367&group_id=180599
>      Network doesn't work anymore switching from kvm-86 to kvm-87
>    

Applied, thanks.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2009-07-08 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08  8:47 [PATCH] net: re-instate some lost vnet_hdr code Mark McLoughlin
2009-07-08 10:20 ` Avi Kivity [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=4A5472FC.1080302@redhat.com \
    --to=avi@redhat.com \
    --cc=akivity@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@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