From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Digimer <linux@alteeve.com>
Cc: xen-devel@lists.xensource.com, Teck Choon Giam <giamteckchoon@gmail.com>
Subject: Re: Trying to adapt Olaf's vif MTU patch for EL5.6's 2.6.18-238.9 kernel - patch in-line.
Date: Mon, 18 Apr 2011 12:22:23 -0400 [thread overview]
Message-ID: <20110418162223.GC20557@dumpdata.com> (raw)
In-Reply-To: <4DAB1A7E.1030409@alteeve.com>
On Sun, Apr 17, 2011 at 12:51:10PM -0400, Digimer wrote:
> I've created two rhbz tickets for these two patches.
>
> Patch for vif MTU:
> https://bugzilla.redhat.com/show_bug.cgi?id=697021
>
> Patch for vif-bridge:
> https://bugzilla.redhat.com/show_bug.cgi?id=697310
You might want to mention where those patches exist upstream. As in,
did you back-port them from 2.6.32, 2.6.38 (or 2.6.39) and if so
what git tree.
next prev parent reply other threads:[~2011-04-18 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 1:44 Trying to adapt Olaf's vif MTU patch for EL5.6's 2.6.18-238.9 kernel - patch in-line Digimer
2011-04-17 3:23 ` Teck Choon Giam
2011-04-17 3:29 ` Digimer
2011-04-17 5:57 ` Digimer
2011-04-17 15:41 ` Digimer
2011-04-17 16:51 ` Digimer
2011-04-18 16:22 ` Konrad Rzeszutek Wilk [this message]
2011-04-18 16:31 ` Digimer
2011-04-19 4:46 ` Digimer
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=20110418162223.GC20557@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=giamteckchoon@gmail.com \
--cc=linux@alteeve.com \
--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 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.