Re: [PATCH] tty: not call tty close in fallback

2019-02-19 Thread Greg KH
On Mon, Jan 14, 2019 at 02:56:01PM +0800, yes wrote: > From: Li RongQing > > when fail to open tty, tty is not in open status and not need > to call close > > Signed-off-by: Li RongQing > --- > drivers/tty/serdev/serdev-ttyport.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > >

Re: [PATCH] tty: not call tty close in fallback

2019-01-13 Thread Jiri Slaby
y...@hpe.com: 550 5.1.1 User Unknown You are sending e-mails/patches from a non-existant address? On 14. 01. 19, 7:56, y...@hpe.com wrote: > From: Li RongQing > > when fail to open tty, tty is not in open status and not need > to call close But tty drivers are special and expect close even on

Re: [PATCH] tty: not call tty close in fallback

2019-01-13 Thread Jiri Slaby
On 14. 01. 19, 7:56, y...@hpe.com wrote: > From: Li RongQing > > when fail to open tty, tty is not in open status and not need > to call close But tty drivers are special and expect close even on failed open, right? See tty_open. > Signed-off-by: Li RongQing > --- > drivers/tty/serdev/serdev-

[PATCH] tty: not call tty close in fallback

2019-01-13 Thread yes
From: Li RongQing when fail to open tty, tty is not in open status and not need to call close Signed-off-by: Li RongQing --- drivers/tty/serdev/serdev-ttyport.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/tty/serdev/serdev-ttyport.c b/drivers/tty/serdev/serd