Re: [PATCH] mos7840: fix chars_in_buffer() return value

2016-09-30 Thread Johan Hovold
On Fri, Sep 30, 2016 at 12:00:30AM +0300, Stas Sergeev wrote: > 29.09.2016 13:09, Johan Hovold пишет: > > On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > >> The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > >> a correct behaviour of that. > >> mos7840 implements

Re: [PATCH] mos7840: fix chars_in_buffer() return value

2016-09-29 Thread Stas Sergeev
29.09.2016 13:09, Johan Hovold пишет: On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch shou

Re: [PATCH] mos7840: fix chars_in_buffer() return value

2016-09-29 Thread Johan Hovold
On Sat, Sep 24, 2016 at 06:00:57PM +0300, Stas Sergeev wrote: > The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on > a correct behaviour of that. > mos7840 implements it wrongly: if you write just one char, TIOCOUTQ > will return 32. > This patch should fix it by accounting the num

[PATCH] mos7840: fix chars_in_buffer() return value

2016-09-24 Thread Stas Sergeev
The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the Tes

Re: [PATCH] mos7840: fix chars_in_buffer() return value

2016-09-24 Thread Stas Sergeev
24.09.2016 16:57, Sergei Shtylyov пишет: Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix i

Re: [PATCH] mos7840: fix chars_in_buffer() return value

2016-09-24 Thread Sergei Shtylyov
Hello. On 9/24/2016 4:47 PM, Stas Sergeev wrote: The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actual

[PATCH] mos7840: fix chars_in_buffer() return value

2016-09-24 Thread Stas Sergeev
The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually written. This patch, unfortunately, misses the Tes

[PATCH] mos7840: fix chars_in_buffer() return value

2016-09-24 Thread Stas Sergeev
The TIOCOUTQ ioctl calls chars_in_buffer(), and some apps depend on a correct behaviour of that. mos7840 implements it wrongly: if you write just one char, TIOCOUTQ will return 32. This patch should fix it by accounting the number of chars actually writCaylan Van Larson ten. This patch, unfortunate

Re: [patch] mos7840: fix chars_in_buffer()

2012-08-16 Thread Greg KH
On Fri, Aug 10, 2012 at 02:38:58PM +0400, Stas Sergeev wrote: > Hello, > > The TIOCOUTQ ioctl calls chars_in_buffer(), and > some apps depend on a correct behaviour of that. > mos7840 implements it wrongly: if you write just > one char, TIOCOUTQ will return 32. > The attached patch should fix it.

[patch] mos7840: fix chars_in_buffer()

2012-08-10 Thread Stas Sergeev
patch. Please review. https://bugzilla.kernel.org/show_bug.cgi?id=45791 Signed-off-by: Stas Sergeev From 02804e64f786d6aaaba54933f7cadd10dff2f497 Mon Sep 17 00:00:00 2001 From: Stas Sergeev Date: Mon, 23 Jul 2012 13:17:40 +0400 Subject: [PATCH] mos7840: fix chars_in_buffer --- drivers/usb/serial