qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 for-2.5 0/3] Net patches for 2.5
Date: Fri, 27 Nov 2015 11:12:20 +0800	[thread overview]
Message-ID: <1448593943-6415-1-git-send-email-jasowang@redhat.com> (raw)

The following changes since commit b04fc428356a540fdb9065fa8c3c71ee476c2031:

  Update version for v2.5.0-rc2 release (2015-11-26 17:50:12 +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 b73c1849148da1229a3c3b336311a8194970b35f:

  tap-win32: disable broken async write path (2015-11-27 10:39:55 +0800)

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

----------------------------------------------------------------
Andrew Baumann (2):
      tap-win32: skip unexpected nodes during registry enumeration
      tap-win32: disable broken async write path

Stefan Weil (1):
      eepro100: Prevent two endless loops

 hw/net/eepro100.c | 16 ++++++++++++++++
 net/tap-win32.c   | 49 ++++++++++++++++++++++++++++++++++++++-----------
 2 files changed, 54 insertions(+), 11 deletions(-)

-- 
2.5.0

             reply	other threads:[~2015-11-27  3:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27  3:12 Jason Wang [this message]
2015-11-27  3:12 ` [Qemu-devel] [PULL for-2.5 1/3] eepro100: Prevent two endless loops Jason Wang
2015-11-27  3:12 ` [Qemu-devel] [PULL for-2.5 2/3] tap-win32: skip unexpected nodes during registry enumeration Jason Wang
2015-11-27  3:12 ` [Qemu-devel] [PULL for-2.5 3/3] tap-win32: disable broken async write path Jason Wang
2015-11-27 11:30 ` [Qemu-devel] [PULL for-2.5 0/3] Net patches for 2.5 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=1448593943-6415-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).