From: jbradford@dial.pipex.com
Message-Id: <200210211617.g9LGHFaO005410@darkstar.example.net>
Subject: Re: Docs for 2.4.x -> 2.6.x
To: rddunlap@osdl.org (Randy.Dunlap)
Date: Mon, 21 Oct 2002 17:17:15 +0100 (BST)
Cc: jbm@joshisanerd.com, linux-kernel@vger.kernel.org
In-Reply-To: <Pine.LNX.4.33L2.0210210853370.29900-100000@dragon.pdx.osdl.net> from "Randy.Dunlap" at Oct 21, 2002 08:55:56 AM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1447
Lines: 36

> On Mon, 21 Oct 2002 jbradford@dial.pipex.com wrote:
> 
> | > Would you volunteer to do the same thing for kernel API changes for those
> | > of us who don't pay enough attention to the list?
> |
> | Well, I'm certainly willing to spare the time to do it, but I'm not
> | sure that I'm particularly qualified to - the 2.4->2.6 doc would be
> | fairly straightforward for me, but documenting API changes in a useful
> | way may well require a better understanding of C than I have, (not
> | sure what I'd be letting myself in for - the only C I've done is
> | mainly games and other user mode stuff).
> |
> | > I have a few random drivers that aren't in mainline, so i always wind up
> | > porting to new kernels (they're trivial, so it's not a big deal, but
> | > sometimes it's annoying to find changes).
> | >
> | > Or is someone else already doing this wonderfully sexy job?
> |
> | It's possible they might be, I'm not sure...
> |
> | John.
> | -
> 
> I got the impression that the first poster was asking
> for user-level 2.4 -> 2.6 migration HOWTO info,
> not kernel API changes.  (such as "be sure that all of those
> CONFIG_INPU_options are enabled!")

Yes, that is really what I meant.

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/