qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] eepro100.c patches
Date: Sat, 19 Dec 2009 16:08:00 +0100	[thread overview]
Message-ID: <4B2CEC50.4040703@mail.berlios.de> (raw)

Hi,

these patches are still missing in QEMU master
(and would also be good for 0.12.x because many
people wait for the multicast fix needed for
junos, see "junos qemu eepro100.c" at google):

089c60f8e467cfd567a946e005f10559b2fb9462
f925f386761fe1abb82aad8472c6fb388b022756
5a89b50ef52e7c9c3cf072638594880fa1a8f596
(apply them in this order to avoid conflicts)

The latest feedback from mst was positive, so I hope
there is nothing more in the way.

Kind regards,
Stefan

             reply	other threads:[~2009-12-19 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 15:08 Stefan Weil [this message]
2009-12-20 14:51 ` [Qemu-devel] eepro100.c patches Anthony Liguori
2009-12-20 15:46   ` Stefan Weil
2009-12-20 15:52     ` [Qemu-devel] [PATCH 1/3] eepro100: Restructure code (new function tx_command) Stefan Weil
2009-12-20 15:52       ` [Qemu-devel] [PATCH 2/3] eepro100: Better documentation for temporary data Stefan Weil
2009-12-20 15:52         ` [Qemu-devel] [PATCH 3/3] eepro100: Fix multicast support Stefan Weil
2009-12-20 16:23         ` [Qemu-devel] [PATCH 2/3] eepro100: Better documentation for temporary data Andreas Färber
2009-12-20 18:05           ` Stefan Weil
2010-01-14 11:19       ` [Qemu-devel] Re: [PATCH 1/3] eepro100: Restructure code (new function tx_command) Michael S. Tsirkin
2009-12-20 16:19     ` [Qemu-devel] eepro100.c patches Anthony Liguori
2010-01-05 21:28       ` Stefan Weil

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=4B2CEC50.4040703@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@us.ibm.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).