From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
yue <ooolinux@163.com>, Digimer <linux@alteeve.com>
Subject: Re: Patches to enable MTUs >1500 in el5.6 ready for testing.
Date: Sat, 23 Apr 2011 19:29:05 +0100 [thread overview]
Message-ID: <1303583345.25988.61.camel@localhost.localdomain> (raw)
In-Reply-To: <20110423174210.GV32595@reaktio.net>
On Sat, 2011-04-23 at 18:42 +0100, Pasi Kärkkäinen wrote:
> On Fri, Apr 22, 2011 at 10:31:42PM -0400, Digimer wrote:
> > On 04/22/2011 09:40 PM, yue wrote:
> > > if the patch will be merged in mainline?
> > > how to get the patch?
> > >
> > > thanks
> >
> > I can't speak to getting it into mainline, but getting it into the Red
> > Hat el5.6 kernel is what I am hoping will happen soon. If you're in a
> > pinch, I can upload the patched files for you to download and test. Of
> > course, that's less preferable than just getting the next RPM updates. :)
> >
>
> The kernel patch is already in xen.git xen/stable-2.6.32.x branch..
> Not sure if it'll be in upstream Linux 2.6.39 netback..
It should be, the two were in sync at the point netback went upstream.
> How about the toolstack (script) patch? Is it already merged in Xen?
>
> -- Pasi
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-23 18:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 23:44 Patches to enable MTUs >1500 in el5.6 ready for testing Digimer
2011-04-23 1:40 ` yue
2011-04-23 2:31 ` Patches " Digimer
2011-04-23 2:38 ` Digimer
2011-04-23 17:42 ` Pasi Kärkkäinen
2011-04-23 18:29 ` Ian Campbell [this message]
2011-04-23 21:52 ` Digimer
2011-04-24 6:47 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2011-04-22 23:44 Madison Kelly
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=1303583345.25988.61.camel@localhost.localdomain \
--to=ian.campbell@citrix.com \
--cc=linux@alteeve.com \
--cc=ooolinux@163.com \
--cc=pasik@iki.fi \
--cc=xen-devel@lists.xensource.com \
/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).