[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170830010716.GC654@jagdpanzerIV.localdomain>
Date: Wed, 30 Aug 2017 10:07:16 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Tejun Heo <tj@...nel.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Pavel Machek <pavel@....cz>, Petr Mladek <pmladek@...e.com>,
Steven Rostedt <rostedt@...dmis.org>, Jan Kara <jack@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Jiri Slaby <jslaby@...e.com>, Andreas Mohr <andi@...as.de>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: printk: what is going on with additional newlines?
On (08/29/17 11:09), Joe Perches wrote:
[..]
> > Introduce a few helper functions for it:
> >
> > init_line_buffer(&buf);
> > print_line(&buf, fmt, args);
> > vprint_line(&buf, fmt, vararg);
> > finish_line(&buf);
> >
> > or whatever, and it sounds like it should be pretty easy to use.
>
> Mostly true and not a new solution.
>
> You'll now need to add &buf to called functions that
> continue individual line output.
>
> Tejun Heo suggested the very similar mprintk back in 2008.
>
> http://thread.gmane.org/gmane.linux.ide/27199
interesting. thanks for the link.
-ss
Powered by blists - more mailing lists