From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL] vhost, netdev, e1000, pci
Date: Tue, 16 Nov 2010 12:35:58 -0200 [thread overview]
Message-ID: <20101116123558.467ed8a5@doriath> (raw)
In-Reply-To: <20101116131620.GA24121@redhat.com>
On Tue, 16 Nov 2010 15:16:20 +0200
"Michael S. Tsirkin" <mst@redhat.com> wrote:
> Here are some fixes I collected in my tree.
> Please merge.
>
> The following changes since commit 5fc9cfedfa09199e10b5f9b67dcd286bfeae4f7a:
>
> Fold send_all() wrapper unix_write() into one function (2010-11-03 12:48:09 -0500)
>
> are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
>
> Alex Williamson (2):
> e1000: Fix TCP checksum overflow with TSO
> PCI: Bus number from the bridge, not the device
>
> Michael S. Tsirkin (3):
> tap: clear vhost_net backend on cleanup
> tap: make set_offload a nop after netdev cleanup
> pci: allow hotplug removal of cold-plugged devices
IMHO it's good practice to re-send patches in the pull request itself,
so that:
1. the submitter knows his/her patches changed from state 'applied in
maintainer's tree' to 'submitted for merging in master'
2. you minimize the risk of merging something that wasn't sent to the
list first
3. people have a chance to review what you picked up, in case they didn't
next prev parent reply other threads:[~2010-11-16 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 13:16 [Qemu-devel] [PULL] vhost, netdev, e1000, pci Michael S. Tsirkin
2010-11-16 14:35 ` Luiz Capitulino [this message]
2010-11-16 14:51 ` Anthony Liguori
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=20101116123558.467ed8a5@doriath \
--to=lcapitulino@redhat.com \
--cc=mst@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).