Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 28 Nov 2002 00:26:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 28 Nov 2002 00:26:08 -0500 Received: from pizda.ninka.net ([216.101.162.242]:34721 "EHLO pizda.ninka.net") by vger.kernel.org with ESMTP id ; Thu, 28 Nov 2002 00:26:06 -0500 Date: Wed, 27 Nov 2002 21:31:48 -0800 (PST) Message-Id: <20021127.213148.94755458.davem@redhat.com> To: torvalds@transmeta.com Cc: sfr@canb.auug.org.au, linux-kernel@vger.kernel.org, anton@samba.org, ak@muc.de, davidm@hpl.hp.com, schwidefsky@de.ibm.com, ralf@gnu.org, willy@debian.org Subject: Re: [PATCH] Start of compat32.h (again) From: "David S. Miller" In-Reply-To: References: <20021127184228.2f2e87fd.sfr@canb.auug.org.au> X-FalunGong: Information control. X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1124 Lines: 27 From: Linus Torvalds Date: Wed, 27 Nov 2002 09:18:06 -0800 (PST) May I just suggest doing a kernel/compat32.c and doing most everything there? I think we're better off that way, even if it means that "do_nanosleep()" etc cannot be static. Please not this, this will continue the current problem we have wherein overhauls of things like VFS infrastructure don't propagate to the compat syscall implementations. Putting the compat stuff right next to the "normal" version has several advantages, one of which is that it is kept in sync with things almost automatically. You have no choice but to notice it, it's right there. This isn't a "oh well we have to export some things" issue, it's a long term maintainence issue. It is the main reason we want to move this into a common area rather than deep within the arch code. - 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/