From: Anthony Liguori <anthony@codemonkey.ws>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PULL] eepro100 patches
Date: Tue, 19 Jan 2010 16:37:10 -0600 [thread overview]
Message-ID: <4B563416.2080207@codemonkey.ws> (raw)
In-Reply-To: <20100119174240.GA3554@redhat.com>
On 01/19/2010 11:42 AM, Michael S. Tsirkin wrote:
> The following changes since commit 1c39457adf220f9011cc6e08c05b272073ec3126:
> Blue Swirl (1):
> Sparc32: Update OpenBIOS image to r666
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu.git for_anthony
>
> Stefan Weil (2):
> eepro100: Restructure code (new function tx_command)
> eepro100: Fix multicast support
>
> hw/eepro100.c | 243 ++++++++++++++++++++++++++++++++-------------------------
> 1 files changed, 137 insertions(+), 106 deletions(-)
>
Pulled. Thanks.
Regards,
Anthony Liguori
prev parent reply other threads:[~2010-01-19 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 17:42 [Qemu-devel] [PULL] eepro100 patches Michael S. Tsirkin
2010-01-19 22:37 ` Anthony Liguori [this message]
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=4B563416.2080207@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=mst@redhat.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).