Re: [PATCH v2] printk: Modify operators of printed_len and text_len

2017-07-11 Thread Petr Mladek
On Tue 2017-07-11 14:40:55, Pierre Kuo wrote: > With commit ("printk: report lost messages in printk > safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks() > function"), it seems we can remove initialization, "=0", of text_len and > directly assign result of log_output to

Re: [PATCH v2] printk: Modify operators of printed_len and text_len

2017-07-11 Thread Petr Mladek
On Tue 2017-07-11 14:40:55, Pierre Kuo wrote: > With commit ("printk: report lost messages in printk > safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks() > function"), it seems we can remove initialization, "=0", of text_len and > directly assign result of log_output to

[PATCH v2] printk: Modify operators of printed_len and text_len

2017-07-11 Thread Pierre Kuo
With commit ("printk: report lost messages in printk safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks() function"), it seems we can remove initialization, "=0", of text_len and directly assign result of log_output to printed_len. Signed-off-by: Pierre Kuo

[PATCH v2] printk: Modify operators of printed_len and text_len

2017-07-11 Thread Pierre Kuo
With commit ("printk: report lost messages in printk safe/nmi contexts") and commit <8b1742c9c207> ("printk: remove zap_locks() function"), it seems we can remove initialization, "=0", of text_len and directly assign result of log_output to printed_len. Signed-off-by: Pierre Kuo Reviewed-by: