[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170206121652.GA2769@pathway.suse.cz>
Date: Mon, 6 Feb 2017 13:16:52 +0100
From: Petr Mladek <pmladek@...e.com>
To: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
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 Mon 2017-02-06 11:08:20, Sergey Senozhatsky wrote:
> 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".
Good point.
> > just in case, the patch (which I prefer to be ignored)
>
> let's keep printk_safe_flush_line().
I do not have strong opinion but I would slightly prefer
to keep the helper function. The use of printk_deferred()
is a bit tricky and it is better to have only one copy.
Steven, could you live with the original patch, please?
Best Regards,
Petr
Powered by blists - more mailing lists