From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261775AbTKBTCi (ORCPT ); Sun, 2 Nov 2003 14:02:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261776AbTKBTCh (ORCPT ); Sun, 2 Nov 2003 14:02:37 -0500 Received: from adsl-63-194-239-202.dsl.lsan03.pacbell.net ([63.194.239.202]:24329 "EHLO mmp-linux.matchmail.com") by vger.kernel.org with ESMTP id S261775AbTKBTCh (ORCPT ); Sun, 2 Nov 2003 14:02:37 -0500 Date: Sun, 2 Nov 2003 11:02:35 -0800 From: Mike Fedyk To: Alexander Chacon Cc: linux-kernel@vger.kernel.org Subject: Re: Modular ipv4 inquiries... Message-ID: <20031102190235.GC3907@matchmail.com> Mail-Followup-To: Alexander Chacon , linux-kernel@vger.kernel.org References: <1067711134.659a9dpacz4s@webmail.mechanus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1067711134.659a9dpacz4s@webmail.mechanus.org> User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Nov 01, 2003 at 12:25:34PM -0600, Alexander Chacon wrote: > Hello! > > I would like to know a few things about making the ipv4 code modular. I've been > working on a school assignment that requires implementing tunneling, but first > ipv4 must be modularized... it needs to be done using kernel 2.4.20 Can you work on the 2.6 tree instead? Thay way your work might have a chance of being integrated when 2.7 starts up.