[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170206020820.GB1750@jagdpanzerIV.localdomain>
Date: Mon, 6 Feb 2017 11:08:20 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jan Kara <jack@...e.cz>, Tejun Heo <tj@...nel.org>,
Calvin Owens <calvinowens@...com>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Peter Hurley <peter@...leysoftware.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv7 4/8] printk: always use deferred printk when flush
printk_safe lines
On (02/06/17 10:48), Sergey Senozhatsky wrote:
[..]
> from many places:
>
> 4x printk_safe_flush_buffer()
> 1x __printk_safe_flush()
>
>
> replacing printk_safe_flush_line() with printk_deferred() produces things
> like these
>
> printk_deferred("%.*s", end - start, start);
> printk_deferred("%.*s", strlen(newline), newline);
ah... besides we need to cast length argument to "int".
> just in case, the patch (which I prefer to be ignored)
let's keep printk_safe_flush_line().
-ss
Powered by blists - more mailing lists