From: Jason Wang <jasowang@redhat.com>
To: qemu-devel@nongnu.org, peter.maydell@linaro.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PULL 0/9] Net patches
Date: Wed, 26 Oct 2016 10:24:02 +0800 [thread overview]
Message-ID: <1477448651-4474-1-git-send-email-jasowang@redhat.com> (raw)
The following changes since commit ede0cbeb7892bdf4a19128853a3a3c61a17fb068:
Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2016-10-25' into staging (2016-10-25 17:03:11 +0100)
are available in the git repository at:
https://github.com/jasowang/qemu.git tags/net-pull-request
for you to fetch changes up to 2061c14c9bea67f8f1fc6bc7acb33c903a0586c1:
colo-proxy: fix memory leak (2016-10-26 09:58:02 +0800)
----------------------------------------------------------------
----------------------------------------------------------------
Brad Smith (1):
tap-bsd: OpenBSD uses tap(4) now
Kevin Wolf (1):
e1000e: Don't zero out buffer address in rx descriptor
Li Qiang (2):
net: eepro100: fix memory leak in device uninit
net: vmxnet: initialise local tx descriptor
Prasad J Pandit (4):
net: pcnet: check rx/tx descriptor ring length
net: pcnet: fix source formatting and indentation
net: rocker: set limit to DMA buffer size
net: rtl8139: limit processing of ring descriptors
Zhang Chen (1):
colo-proxy: fix memory leak
hw/net/e1000e_core.c | 8 +--
hw/net/eepro100.c | 1 +
hw/net/pcnet.c | 133 ++++++++++++++++++++++++++-----------------------
hw/net/rocker/rocker.c | 2 +-
hw/net/rtl8139.c | 2 +-
hw/net/vmxnet3.c | 1 +
net/colo-compare.c | 34 ++++++-------
net/filter-rewriter.c | 17 ++-----
net/tap-bsd.c | 6 ++-
net/trace-events | 1 +
10 files changed, 104 insertions(+), 101 deletions(-)
--
2.7.4
next reply other threads:[~2016-10-26 2:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 2:24 Jason Wang [this message]
2016-10-26 2:24 ` [Qemu-devel] [PULL 1/9] net: pcnet: check rx/tx descriptor ring length Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 2/9] net: pcnet: fix source formatting and indentation Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 3/9] tap-bsd: OpenBSD uses tap(4) now Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 4/9] net: eepro100: fix memory leak in device uninit Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 5/9] net: rocker: set limit to DMA buffer size Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 6/9] e1000e: Don't zero out buffer address in rx descriptor Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 7/9] net: vmxnet: initialise local tx descriptor Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 8/9] net: rtl8139: limit processing of ring descriptors Jason Wang
2016-10-26 2:24 ` [Qemu-devel] [PULL 9/9] colo-proxy: fix memory leak Jason Wang
2016-10-30 12:13 ` Greg Kurz
2016-10-31 6:37 ` Zhang Chen
2016-10-31 7:40 ` Jason Wang
2016-10-31 8:05 ` Zhang Chen
2016-10-31 9:30 ` Greg Kurz
2016-10-27 12:31 ` [Qemu-devel] [PULL 0/9] Net patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2018-03-05 3:11 Jason Wang
2018-03-05 15:16 ` Peter Maydell
2017-05-23 2:43 Jason Wang
2017-05-23 13:54 ` Stefan Hajnoczi
2015-05-11 15:26 Stefan Hajnoczi
2015-05-12 10:41 ` Peter Maydell
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=1477448651-4474-1-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=peter.maydell@linaro.org \
--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).