- 13 Oct, 2018 40 commits
-
-
Al Viro authored
the only user is very old setserial rc script and even that (as far back as MCC Interim, AFAICS) doesn't actually fail - just gives one message during the boot ("Cannot scan for wild interrupts") and proceeds past that just fine. Signed-off-by:Al Viro <viro@zeniv.linux.org.uk>
-
Al Viro authored
compat_ptr() for pointer-taking ones... Signed-off-by: -
Al Viro authored
pointer-taking ones need compat_ptr(); int-taking one doesn't. Signed-off-by: -
Al Viro authored
all of those are provided only by vt and s390 tty3270; both have proper ->compat_ioctl() Signed-off-by: -
Al Viro authored
... and get rid of COMPAT_IOCTL() for its private ioctls Signed-off-by: -
Al Viro authored
we need it for "convert the structure" cases too Signed-off-by: -
Al Viro authored
especially when you've just copied it in... Signed-off-by: -
Al Viro authored
for pity sake, that case is identical to their default: _and_ bears an explicit comment re leaving to ldisc. Which is what default is doing, obviously... Signed-off-by: -
Al Viro authored
no point duplicating that in tty_operations ->ioctl() Signed-off-by: -
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:
-
