qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: peter.maydell@linaro.org, qemu-devel@nongnu.org
Cc: Jason Wang <jasowang@redhat.com>
Subject: [Qemu-devel] [PULL 0/6] Net patches
Date: Fri, 20 Jan 2017 11:07:44 +0800	[thread overview]
Message-ID: <1484881670-24237-1-git-send-email-jasowang@redhat.com> (raw)

The following changes since commit 0f6bcf68a99efdc531b209551f2b760b0bdcc554:

  Merge remote-tracking branch 'remotes/artyom/tags/pull-sun4v-20170118' into staging (2017-01-19 18:34:13 +0000)

are available in the git repository at:

  https://github.com/jasowang/qemu.git tags/net-pull-request

for you to fetch changes up to fac7d7b1cdb21f921d7ac396365f5e920ef03096:

  tap: fix memory leak on failure in net_init_tap() (2017-01-20 10:58:26 +0800)

----------------------------------------------------------------

----------------------------------------------------------------
Alex Kompel (1):
      hw/pci: use-after-free in pci_nic_init_nofail when nic device fails to initialize

Ladi Prosek (1):
      net: optimize checksum computation

Peter Maydell (2):
      hw/net/dp8393x: Avoid unintentional sign extensions on addresses
      tap: fix memory leak on failure in net_init_tap()

Thomas Huth (1):
      m68k: QOMify the MCF Fast Ethernet Controller device

Zhang Chen (1):
      docs: Fix description of the sentence

 docs/colo-proxy.txt       |  4 +-
 hw/m68k/mcf5208.c         | 25 ++++++++++++-
 hw/net/dp8393x.c          | 95 +++++++++++++++++++++++++++++++++--------------
 hw/net/mcf_fec.c          | 71 ++++++++++++++++++++++++++---------
 hw/pci/pci.c              |  9 +----
 include/hw/m68k/mcf.h     |  4 --
 include/hw/m68k/mcf_fec.h | 13 +++++++
 net/checksum.c            | 21 +++++++----
 net/tap.c                 |  7 +++-
 9 files changed, 180 insertions(+), 69 deletions(-)
 create mode 100644 include/hw/m68k/mcf_fec.h

             reply	other threads:[~2017-01-20  3:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20  3:07 Jason Wang [this message]
2017-01-20  3:07 ` [Qemu-devel] [PULL 1/6] docs: Fix description of the sentence Jason Wang
2017-01-20  3:07 ` [Qemu-devel] [PULL 2/6] net: optimize checksum computation Jason Wang
2017-01-20  3:07 ` [Qemu-devel] [PULL 3/6] m68k: QOMify the MCF Fast Ethernet Controller device Jason Wang
2017-01-20  3:07 ` [Qemu-devel] [PULL 4/6] hw/net/dp8393x: Avoid unintentional sign extensions on addresses Jason Wang
2017-01-20  3:07 ` [Qemu-devel] [PULL 5/6] hw/pci: use-after-free in pci_nic_init_nofail when nic device fails to initialize Jason Wang
2017-01-20  3:07 ` [Qemu-devel] [PULL 6/6] tap: fix memory leak on failure in net_init_tap() Jason Wang
2017-01-20 15:53 ` [Qemu-devel] [PULL 0/6] Net patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2018-04-10  3:39 Jason Wang
2018-04-10 13:04 ` Peter Maydell
2018-01-29  8:16 Jason Wang
2018-01-29  8:25 ` no-reply
2018-01-29 10:02   ` Jason Wang
2018-01-29 10:58     ` Thomas Huth
2018-01-29 12:30       ` Jason Wang
2018-01-29 15:52 ` Peter Maydell
2017-11-20  3:31 Jason Wang
2017-11-20  3:44 ` no-reply
2017-11-20  4:39   ` Thomas Huth
2017-11-20 17:59 ` Peter Maydell
2015-02-06 14:10 Stefan Hajnoczi
2015-02-06 16:10 ` 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=1484881670-24237-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).