lkml.org 
[lkml]   [2001]   [Aug]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: ioctl conflicts
From
Date
"David S. Miller" <davem@redhat.com> writes:

|> From: Alan Cox <alan@lxorguk.ukuu.org.uk>
|> Date: Thu, 30 Aug 2001 09:20:45 +0100 (BST)
|>
|> > I was grep-ing on a 2.4 source tree when i found the
|> > following :
|> >
|> > ./include/linux/videodev.h:#define VIDIOCGCAP
|> > _IOR('v',1,struct video_capability)
|> > ./include/linux/ext2_fs.h:#define EXT2_IOC_GETVERSION _IOR('v',1,
|> > long)
|>
|> Thats fine. ext2 ioctls and video ioctls go to different places
|>
|> Consider sparc64.

These ioctl numbers are different due to the different argument size, so
there should be no conflict.

Andreas.

--
Andreas Schwab "And now for something
SuSE Labs completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
-
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/

\
 
 \ /
  Last update: 2005-03-22 13:01    [from the cache]
©2003-2011 Jasper Spaans