xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen@lists.fedoraproject.org" <xen@lists.fedoraproject.org>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out)
Date: Wed, 16 Nov 2011 16:34:56 +0000	[thread overview]
Message-ID: <CAE996B0.34330%keir@xen.org> (raw)
In-Reply-To: <20111116155347.GI12984@reaktio.net>

On 16/11/2011 15:53, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:

> On Wed, Nov 16, 2011 at 03:00:25PM +0000, Keir Fraser wrote:
>> On 16/11/2011 13:33, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:
>> 
>>> On Mon, Nov 14, 2011 at 05:47:11PM +0000, Ian Jackson wrote:
>>>> Pasi Kärkkäinen writes ("Re: [Xen-devel] [PATCH] Xen 4.1.2 HVM guest
>>>> realtek
>>>> nic problems (eth0 8139cp transmit queue timed out)"):
>>>>> So please go ahead and commit the fix to xen-4.1-testing.hg.
>>>> 
>>>> Keir, will you do this ?  If you prefer I can do it, but I need the
>>>> blessing of a hypervisor maintainer.
>>>> 
>>> 
>>> Ping? 
>> 
>> I responded on 3rd November:
>> 
>> "This looks like a backport of Stefano's xen-unstable c/s 24007. I would
>> like him to submit/ack the backport, as it is not a trivial backport of the
>> xen-unstable patch."
>> 
> 
> Stefano already submitted a new patch for this..

So he did. I've now applied it to xen-4.1-testing.

 -- Keir

> -- Pasi
> 

  parent reply	other threads:[~2011-11-16 16:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 18:49 Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) Pasi Kärkkäinen
2011-10-31 18:52 ` Pasi Kärkkäinen
2011-10-31 19:24 ` Boris Derzhavets
2011-10-31 19:29   ` [Fedora-xen] [Xen-devel] " Pasi Kärkkäinen
2011-11-01 20:56     ` [Fedora-xen] [Xen-devel] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) [PATCH] Pasi Kärkkäinen
2011-11-03 18:07       ` [Fedora-xen] [Xen-devel] [PATCH] Xen 4.1.2 HVM guest realtek nic problems (eth0 8139cp transmit queue timed out) Pasi Kärkkäinen
2011-11-03 18:34         ` Keir Fraser
2011-11-07 12:02           ` [Fedora-xen] [Xen-devel] " Stefano Stabellini
2011-11-08 11:24             ` Pasi Kärkkäinen
2011-11-11  7:02               ` Pasi Kärkkäinen
2011-11-14 17:39                 ` Pasi Kärkkäinen
     [not found]                 ` <m2n.s.1RQ0WH-146660@chiark.greenend.org.uk>
2011-11-14 17:47                   ` Ian Jackson
2011-11-16 13:33                     ` Pasi Kärkkäinen
2011-11-16 15:00                       ` Keir Fraser
2011-11-16 15:53                         ` [Fedora-xen] [Xen-devel] " Pasi Kärkkäinen
2011-11-16 16:01                           ` Pasi Kärkkäinen
2011-11-16 16:03                           ` M A Young
2011-11-16 16:34                           ` Keir Fraser [this message]
2011-11-16 16:44                             ` Pasi Kärkkäinen

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=CAE996B0.34330%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@lists.fedoraproject.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).