From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: ELKS kernel source Date: 05 Jun 2002 23:58:35 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1023310714.2411.18.camel@cool> References: Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="iso-8859-7" To: Riley Williams Cc: Alan Cox , Linux 8086 =D4=E7=ED =D4=E5=F4, 05-06-2002 =F3=F4=E9=F2 19:51, =EF/=E7 Riley Willi= ams =DD=E3=F1=E1=F8=E5: > Hi Alan, Harry. >=20 > As per my recent email, I have now completed the important part of th= e > ELKS kernel ANSI'fication and lint-checking using the splint tool. Du= e > to other commitments, I won't get a chance to do any further developm= ent > on the ELKS source tree until Saturday 14th June 2002, so if you want= to > hammer what I've done into some other shape, please go ahead. >=20 > With regard to the problem that currently prevents the ktcp tool from > working, my testing indicates that the problem is NOT in the tcpdev.c > source file, and I am currently at a loss as to precicely what the > problem is. >=20 > For those wishing to have a working ktcp under ELKS, I have assigned = two > tags in the CVS repository: >=20 > 1. elks-0_1_1-pre1-last is the last kernel in the CVS repository > for which the kctp tool works. >=20 > 2. elks-0_1_1-pre2 is the first kernel in the CVS repository for > which the ktcp tool fails. >=20 > Somewhere between those two patchsets is the tweak that causes ktcp t= o > panic, but I have been unable to find it so far and, as stated above, > I'm not likely to get a chance to do any more testing until the 14th. > Any help sorting this out will be very much appreciated. >=20 > Best wishes from Riley. >=20 I will look in to it... Harry - To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html