From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S1030330AbVLMWvV@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1030330AbVLMWvV (ORCPT <rfc822;willy@w.ods.org>);
	Tue, 13 Dec 2005 17:51:21 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030282AbVLMWvV
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 13 Dec 2005 17:51:21 -0500
Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:57543
	"EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP
	id S1030276AbVLMWvU (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 13 Dec 2005 17:51:20 -0500
Date: Tue, 13 Dec 2005 14:51:09 -0800 (PST)
Message-Id: <20051213.145109.20744871.davem@davemloft.net>
To: matthew@wil.cx
Cc: hch@lst.de, akpm@osdl.org, linux-kernel@vger.kernel.org,
       linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/3] sanitize building of fs/compat_ioctl.c
From: "David S. Miller" <davem@davemloft.net>
In-Reply-To: <20051213173434.GP9286@parisc-linux.org>
References: <20051213172325.GC16392@lst.de>
	<20051213173434.GP9286@parisc-linux.org>
X-Mailer: Mew version 4.2.53 on Emacs 21.4 / 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

From: Matthew Wilcox <matthew@wil.cx>
Date: Tue, 13 Dec 2005 10:34:34 -0700

> The 64-bit code doesn't compile because Andi keeps blocking the
> is_compat_task() stuff.

The one place where I ever thought that was necessary, the
USB async userspace I/O operation stuff, was solved much more
cleanly with ->compat_ioctl() file_operations handlers.

What do you really still need it for at this point?

I also would like to avoid it if possible.