Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 10 Sep 2002 20:17:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 10 Sep 2002 20:17:01 -0400 Received: from smtpzilla5.xs4all.nl ([194.109.127.141]:50185 "EHLO smtpzilla5.xs4all.nl") by vger.kernel.org with ESMTP id ; Tue, 10 Sep 2002 20:17:00 -0400 Date: Wed, 11 Sep 2002 02:20:25 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@serv To: Jeff Garzik cc: linux-kernel , kbuild-devel Subject: Re: linux kernel conf 0.5 In-Reply-To: <3D7E83F4.6050302@mandrakesoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 31 Hi On Tue, 10 Sep 2002, Jeff Garzik wrote: > How about posting a kernel patch (or link to one) that you feel is > suitable for 2.5.x integration? That makes it a bit easier to review in > context, and may help to resolve any final integration issues. That depends on what you want to see. The package itself is installed under scripts/lkc ("make install" just makes a symlink) and is pretty much the same you find in the archive (minus the converter). A problem here is that the current kbuild can't deal with C++ files and builds too much even if you just want a single target, so it's currently not using the kbuild infrastructure. The other big part are the converted config files, they are currently generated as Config.new, so they can be easily removed again. A "final" patch would be hardly readable. Installing (and uninstalling) the package into a kernel tree is quite simple, so I prefer to do it this way to save bandwidth. > For the record I like what I've seen so far... Thanks. :) bye, Roman - 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/