All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Steven Smith <steven.smith@citrix.com>
Cc: Steven Smith <Steven.Smith@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Andreas Florath <xen@flonatel.org>
Subject: Re: Strange error in domU after dom0 update
Date: Wed, 04 Nov 2009 13:04:07 -0800	[thread overview]
Message-ID: <4AF1EC47.5000109@goop.org> (raw)
In-Reply-To: <20091104090453.GA1611@weybridge.uk.xensource.com>

On 11/04/09 01:04, Steven Smith wrote:
>> Looks good for me: reinstalled everything with patched version - iSCSI  
>> functionality and performance is ok. No errors / warnings about  
>> 'netfront: rx->offset' any more.
>>     
> Great.  Thanks for testing this.
>
> Could you apply the patch to your tree, please, Jeremy?
>   

It should already be there.  I applied it shortly after you posted it,
since it looked reasonable independent of whether it solved Andreas's
problem.

    J

  reply	other threads:[~2009-11-04 21:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22  7:47 Strange error in domU after dom0 update Andreas Florath
2009-10-22 11:01 ` Pasi Kärkkäinen
2009-10-22 11:55   ` Andreas Florath
2009-10-22 21:08     ` Jeremy Fitzhardinge
2009-10-23 11:28       ` Andreas Florath
2009-10-23 16:01         ` Andreas Florath
2009-10-27 14:44           ` Andreas Florath
2009-10-27 18:29             ` Jeremy Fitzhardinge
2009-10-29 11:14               ` Andreas Florath
2009-10-29 22:11                 ` Jeremy Fitzhardinge
2009-10-30  9:24                   ` Andreas Florath
2009-10-30 11:11                     ` Steven Smith
2009-11-02  8:59                       ` xen
2009-11-03 10:29                       ` Andreas Florath
2009-11-03 22:52                         ` Jeremy Fitzhardinge
2009-11-04  9:04                         ` Steven Smith
2009-11-04 21:04                           ` Jeremy Fitzhardinge [this message]
2009-11-05 12:22                             ` Steven Smith

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=4AF1EC47.5000109@goop.org \
    --to=jeremy@goop.org \
    --cc=Steven.Smith@eu.citrix.com \
    --cc=steven.smith@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen@flonatel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.