Re: [PATCH 04/50] mos7720: bury dead TIOCM... in ->ioctl()

2018-09-14 Thread Johan Hovold
On Thu, Sep 13, 2018 at 03:40:03AM +0100, Al Viro wrote: > From: Al Viro > > 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

Re: [PATCH 04/50] mos7720: bury dead TIOCM... in ->ioctl()

2018-09-14 Thread Johan Hovold
On Thu, Sep 13, 2018 at 03:40:03AM +0100, Al Viro wrote: > From: Al Viro > > 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

[PATCH 04/50] mos7720: bury dead TIOCM... in ->ioctl()

2018-09-12 Thread Al Viro
From: Al Viro 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: Al Viro ---

[PATCH 04/50] mos7720: bury dead TIOCM... in ->ioctl()

2018-09-12 Thread Al Viro
From: Al Viro 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: Al Viro ---