Messages in this thread |  | | Date | Thu, 30 Aug 2001 02:29:17 -0700 (PDT) | | Subject | Re: ioctl conflicts | | From | "David S. Miller" <> |
| |
From: Alan Cox <alan@lxorguk.ukuu.org.uk> Date: Thu, 30 Aug 2001 10:14:45 +0100 (BST)
> Thats fine. ext2 ioctls and video ioctls go to different places > Consider sparc64. If the ioctl translation layer can't handle duplicates it has bigger problems than that
How else can the current scheme translate arguments correctly if the ioctl values are identical?
Let's say that the video info struct is two ints, right? That would make the two ioctl values in question be identical.
I agree whole-heartedly that the current scheme is flawed, what really should happen is that the translations occur in the ioctl handlers themselves, not in some funny sparc port sources.
That is something I will be doing in 2.5.x, for sure.
Later, David S. Miller davem@redhat.com - 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/
|  |