Re: [PATCH 2/2] add a dev_ioctl fallback to sock_ioctl

2006-01-03 Thread David S. Miller
From: Christoph Hellwig <[EMAIL PROTECTED]> Date: Tue, 27 Dec 2005 19:53:05 +0100 > Currently all network protocols need to call dev_ioctl as the default > fallback in their ioctl implementations. This patch adds a fallback > to dev_ioctl to sock_ioctl if the protocol returned -ENOIOCTLCMD. > Thi

Re: [PATCH 2/2] add a dev_ioctl fallback to sock_ioctl

2005-12-28 Thread Christoph Hellwig
On Wed, Dec 28, 2005 at 12:17:11AM +0300, Michael Tokarev wrote: > There's something wrong with this new `return' statement. > On my screen it looks like a 'diamond' character instead > of a minus sign -- a character with code 0xAD ;) That's true. Due to some funky terminal interactions I had thi

Re: [PATCH 2/2] add a dev_ioctl fallback to sock_ioctl

2005-12-27 Thread Michael Tokarev
Christoph Hellwig wrote: Currently all network protocols need to call dev_ioctl as the default fallback in their ioctl implementations. This patch adds a fallback to dev_ioctl to sock_ioctl if the protocol returned -ENOIOCTLCMD. This way all the procotol ioctl handlers can be simplified and we d

[PATCH 2/2] add a dev_ioctl fallback to sock_ioctl

2005-12-27 Thread Christoph Hellwig
Currently all network protocols need to call dev_ioctl as the default fallback in their ioctl implementations. This patch adds a fallback to dev_ioctl to sock_ioctl if the protocol returned -ENOIOCTLCMD. This way all the procotol ioctl handlers can be simplified and we don't need to export dev_ioc