Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 4 Oct 2002 10:56:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 4 Oct 2002 10:54:38 -0400 Received: from hermes.fachschaften.tu-muenchen.de ([129.187.202.12]:58613 "HELO hermes.fachschaften.tu-muenchen.de") by vger.kernel.org with SMTP id ; Fri, 4 Oct 2002 10:54:04 -0400 Date: Fri, 4 Oct 2002 16:59:32 +0200 (CEST) From: Adrian Bunk X-X-Sender: bunk@mimas.fachschaften.tu-muenchen.de To: linux-kernel@vger.kernel.org Subject: Why does x86_64 support a SuSE-specific ioctl? 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: 902 Lines: 39 Hi, arch/x86_64/ia32/ia32_ioctl.c in both 2.4.20-pre8 and 2.5.40 contains: <-- snip --> ... /* SuSE extension */ #ifndef TIOCGDEV #define TIOCGDEV _IOR('T',0x32, unsigned int) #endif static int tiocgdev(unsigned fd, unsigned cmd, unsigned int *ptr) { ... } ... HANDLE_IOCTL(TIOCGDEV, tiocgdev) ... <-- snip --> TIOCGDEV is (as the comment above indicates) in neither 2.4.20-pre9 nor in 2.5.40 and I'm wondering why the x86_64 kernel supports a SuSE-specific i386 ioctl? cu Adrian -- You only think this is a free country. Like the US the UK spends a lot of time explaining its a free country because its a police state. Alan Cox - 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/