From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PULL REQUEST] merge latest upstream qemu networking bits
Date: Mon, 02 Nov 2009 12:36:30 +0200 [thread overview]
Message-ID: <4AEEB62E.4090206@redhat.com> (raw)
In-Reply-To: <1256739546.5105.48.camel@blaa>
On 10/28/2009 04:19 PM, Mark McLoughlin wrote:
> Hey,
>
> Below is a pull request to merge latest qemu.git/master into
> qemu-kvm.git/next
>
>
Pulled, thanks.
> The most notable thing here is that all our networking changes are now
> upstream - i.e. there are no longer qemu-kvm specific changes to
> net.[ch], net-queue.[ch], savevm.c and hw/virtio-net.c
>
> This has resulted in one intentional regression - in order to use GSO,
> you must now use '-netdev tap' rather than '-net tap'. We could continue
> to support the latter, but it's never going upstream so we may as well
> drop it now.
>
> Another regression is that virtio-net loses it's MAC address, but I've
> just sent a fix for that to qemu-devel.
>
What does this mean? It loses the ability to set it?
> The merge wasn't as straightforward as one might have hoped because many
> of the intermediate upstream commits weren't actually buildable because
> the patches were mangled as they were applied. I took the approach of
> merging those unbuildable commits individually and applying a fixup
> patch, so each merge commit should be buildable. Those fixup changes
> went away in later merges.
>
Great, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-02 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 14:19 [PULL REQUEST] merge latest upstream qemu networking bits Mark McLoughlin
2009-11-02 10:36 ` Avi Kivity [this message]
2009-11-02 11:57 ` Mark McLoughlin
2009-11-02 12:04 ` Avi Kivity
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=4AEEB62E.4090206@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=mtosatti@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