qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anthony Liguori <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL 0/4] Net patches
Date: Mon, 27 Jan 2014 15:48:45 +0100	[thread overview]
Message-ID: <1390834129-19625-1-git-send-email-stefanha@redhat.com> (raw)

The following changes since commit 0169c511554cb0014a00290b0d3d26c31a49818f:

  Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2014-01-24 15:52:44 -0800)

are available in the git repository at:


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

for you to fetch changes up to 1f149e721feb617d14a3ee4f5911c47b29866a54:

  tap-linux: Get features once and use it many times (2014-01-27 15:44:06 +0100)

----------------------------------------------------------------
Net patches

----------------------------------------------------------------
Hani Benhabiles (1):
      net: Use g_strdup_printf instead of snprintf.

Kusanagi Kouichi (1):
      tap-linux: Get features once and use it many times

Roy Franz (2):
      Fix lan9118 TX "CMD A" handling
      Fix lan9118 buffer length handling

 hw/net/lan9118.c |  6 +++---
 net/net.c        |  5 +----
 net/tap-linux.c  | 14 ++++++++------
 3 files changed, 12 insertions(+), 13 deletions(-)

-- 
1.8.4.2

             reply	other threads:[~2014-01-27 14:49 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 14:48 Stefan Hajnoczi [this message]
2014-01-27 14:48 ` [Qemu-devel] [PULL 1/4] net: Use g_strdup_printf instead of snprintf Stefan Hajnoczi
2014-01-27 14:48 ` [Qemu-devel] [PULL 2/4] Fix lan9118 TX "CMD A" handling Stefan Hajnoczi
2014-01-27 14:48 ` [Qemu-devel] [PULL 3/4] Fix lan9118 buffer length handling Stefan Hajnoczi
2014-01-27 14:48 ` [Qemu-devel] [PULL 4/4] tap-linux: Get features once and use it many times Stefan Hajnoczi
2014-01-31  0:09 ` [Qemu-devel] [PULL 0/4] Net patches Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2019-05-17  9:06 Jason Wang
2019-05-17 14:46 ` Peter Maydell
2018-06-15  3:01 Jason Wang
2018-06-15 11:49 ` Peter Maydell
2018-05-14  7:55 Jason Wang
2018-05-14 16:52 ` Peter Maydell
2015-09-17 11:43 Stefan Hajnoczi
2015-09-17 13:29 ` Peter Maydell
2015-06-05 10:22 Stefan Hajnoczi
2015-06-05 12:52 ` Peter Maydell
2015-01-12 10:27 Stefan Hajnoczi
2015-01-12 12:01 ` Peter Maydell
2013-12-09 13:11 Stefan Hajnoczi
2013-10-18 13:35 Stefan Hajnoczi
2013-09-02 11:38 Stefan Hajnoczi
2013-09-05 18:38 ` Anthony Liguori
2013-09-06 14:59   ` Stefan Hajnoczi
2013-09-05 19:49 ` Paolo Bonzini
2013-09-05 21:02   ` Aurelien Jarno
2013-09-06  6:03     ` Paolo Bonzini
2013-09-06 14:59       ` Stefan Hajnoczi
2013-09-09 14:49         ` Aurelien Jarno
2013-09-10  7:49           ` Stefan Hajnoczi
2013-01-08 10:45 Stefan Hajnoczi
2013-01-08 20:34 ` Anthony Liguori
2012-11-16 13:40 Stefan Hajnoczi
2012-10-08 12:02 Stefan Hajnoczi
2012-10-12 16:18 ` 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=1390834129-19625-1-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=aliguori@amazon.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).