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
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
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
---
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
---
4 matches
Mail list logo