- Oct 13, 2018
-
-
Al Viro authored
no point duplicating that in tty_operations ->ioctl() Signed-off-by:Al Viro <viro@zeniv.linux.org.uk>
-
Al Viro authored
none of them handles it anyway. Reviewed-by:
Johan Hovold <johan@kernel.org> Signed-off-by:
-
Al Viro authored
kill the dead code, especially since ->break_ctl() will do the right thing anyway. Signed-off-by: -
Al Viro authored
TIOCLINUX is handled by ->compat_ioctl() in the only place that has native ->ioctl() recognizing it, TIOC{START,STOP} are simply useless these days - unrecognized compat ioctl won't spew into syslog anymore. Signed-off-by: -
Al Viro authored
bury the dead code (and ->tiocmget()/->tiocmset() are there, so I really wonder why have they kept the stuff that became unreachable with the introduction of those...) Signed-off-by: -
Al Viro authored
kill the long-dead code - it's been unreachable since 2008. Redundant, as well - generic will do exact same thing, since ->break_ctl is NULL here... Signed-off-by: -
Al Viro authored
NULL ->ioctl() in tty_operations is treated as "returns -ENOIOCTLCMD"... Signed-off-by: -
Al Viro authored
Signed-off-by: -
Al Viro authored
it's never getting called with TIOC[SG]SERIAL anymore (nor has it ever supported those, while we are at it) Signed-off-by: -
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
... and fix the return value - on success it used to have ioctl(2) fill the user-supplied struct serial_struct and return -ENOTTY. Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Signed-off-by: -
Al Viro authored
add such methods for usb_serial_driver, provide tty_operations ->[sg]et_serial() calling those. For now the lack of methods in driver means ENOIOCTLCMD from usb-serial ->[sg]et_serial(), making tty_ioctl() fall back to calling ->ioctl(). Once all drivers are converted, we'll be returning -ENOTTY instead, completing the switchover. Reviewed-by:
-
Al Viro authored
no support there Signed-off-by: -
Al Viro authored
Signed-off-by: -
Al Viro authored
Signed-off-by: -
Al Viro authored
Pointless dead assignments in moxa_set_serial_info() killed off; they would've been a bug, if not for the fact that user-settable flags had never been used in that driver. Bogus from day 1, though... Signed-off-by: -
Al Viro authored
Signed-off-by: -
Al Viro authored
Acked-by:
David Sterba <dsterba@suse.com> Signed-off-by:
-
Al Viro authored
Signed-off-by: -
Al Viro authored
Signed-off-by:
-
- Sep 14, 2018
-
-
Al Viro authored
Reviewed-by:
-
Al Viro authored
Signed-off-by: -
Al Viro authored
Signed-off-by: -
Al Viro authored
->set_serial() and ->get_serial() resp., both taking tty and a kernel pointer to serial_struct. Signed-off-by: -
Al Viro authored
These ioctls never reach driver's ->ioctl() - tty_ioctl() handles them on its own. ->tiocm[gs]et() is what actually gets called, and mos7720 provides those, with results equivalent to what the unreachable code would be doing when called. Signed-off-by:
-
