From: Lee Revell <rlrevell@joe-job.com>
To: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Cc: davem@davemloft.net, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@redhat.com, yoshfuji@linux-ipv6.org, kaber@coreworks.de,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.8.1 to linux-2.6.10: Kernel Patching Issues.
Date: Fri, 25 Feb 2005 11:47:23 -0500 [thread overview]
Message-ID: <1109350044.9681.26.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.10.10502251550520.26208-100000@mtfhpc.demon.co.uk>
On Fri, 2005-02-25 at 16:40 +0000, Mark Fortescue wrote:
> Hi all,
>
> I am not sure exactly where to send this email. A have chosen the
> ip4/ip6 networking as the issues are in this area of the kernel.
>
> The kernel patch files patch-2.6.9 and patch-2.6.10 do not apear to be
> correct.
No, you're doing it wrong. 2.6.8.1 was a bugfix release. The correct
patching order is 2.6.8 -> 2.6.9 -> 2.6.10.
Lee
next prev parent reply other threads:[~2005-02-25 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 16:40 linux-2.6.8.1 to linux-2.6.10: Kernel Patching Issues Mark Fortescue
2005-02-25 16:47 ` Lee Revell [this message]
2005-02-25 17:12 ` Tim Schmielau
2005-02-25 17:53 ` Mark Fortescue
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=1109350044.9681.26.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=kaber@coreworks.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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).