qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] eepro100: Don't allow guests to fail assertions
Date: Fri, 25 Sep 2009 12:14:45 +0200	[thread overview]
Message-ID: <4ABC9815.4010007@redhat.com> (raw)
In-Reply-To: <4ABA62D3.6030900@mail.berlios.de>

Am 23.09.2009 20:02, schrieb Stefan Weil:
> There are about 10 pending patches for eepro100.c, so the code at
> savannah is
> not a good base for new patches of eepro100.c. And there are even more
> patches
> in my queue to be sent as soon as the first 10 are integrated.

On second thought, your 10+ patches are only for master, I assume? Then
this patch should be applied in its current version to the stable
branch(es). I'll still rebase for master, of course.

Kevin

  parent reply	other threads:[~2009-09-25 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 15:42 [Qemu-devel] [PATCH] eepro100: Don't allow guests to fail assertions Kevin Wolf
2009-09-23 18:02 ` Stefan Weil
2009-09-24  7:25   ` Kevin Wolf
2009-09-25 10:14   ` Kevin Wolf [this message]
2009-09-25 15: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=4ABC9815.4010007@redhat.com \
    --to=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).