From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Cc: Mark Fortescue <mark@mtfhpc.demon.co.uk>
Subject: Re: linux-2.6.8.1 to linux-2.6.10: Kernel Patching Issues.
Date: Fri, 25 Feb 2005 17:48:42 +0100 [thread overview]
Message-ID: <200502251748.43447.lkml@kcore.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10502251550520.26208-100000@mtfhpc.demon.co.uk>
On Friday 25 February 2005 17:40, 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. I had some errors during patching so I generated a diff against a
> freshly downloaded linux-2.6.10 kernel. See the steps below:
You first have to go back to kernel 2.6.8, and then patch upwards to 2.6.9 and
2.6.10. Don't patch upwards from 2.6.8.1.
Jan
--
It's better to burn out than to fade away.
next prev parent reply other threads:[~2005-02-25 16:49 UTC|newest]
Thread overview: 6+ 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
2005-02-25 16:55 ` Tomasz Torcz
2005-02-25 16:48 ` Jan De Luyck [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=200502251748.43447.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@mtfhpc.demon.co.uk \
/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.