From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751991AbdH2X71 (ORCPT <rfc822;w@1wt.eu>);
        Tue, 29 Aug 2017 19:59:27 -0400
Received: from mail-io0-f180.google.com ([209.85.223.180]:35363 "EHLO
        mail-io0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751318AbdH2X7Z (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Tue, 29 Aug 2017 19:59:25 -0400
MIME-Version: 1.0
In-Reply-To: <20170829195013.5048dc42@gandalf.local.home>
References: <20170815025625.1977-1-sergey.senozhatsky@gmail.com>
 <20170828090521.GA25025@amd> <20170828102830.GA403@jagdpanzerIV.localdomain>
 <20170828122109.GA532@jagdpanzerIV.localdomain> <20170828124634.GD492@amd>
 <20170829134048.GA437@jagdpanzerIV.localdomain> <CA+55aFwmwdY_mMqdEyFPpRhCKRyeqj=+aCqe5nN108v8ELFvPw@mail.gmail.com>
 <CA+55aFyzR4LKhJKLFgvvd9OTsos2_g4-9fova782BX4kyA3bLA@mail.gmail.com> <20170829195013.5048dc42@gandalf.local.home>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Tue, 29 Aug 2017 16:59:24 -0700
X-Google-Sender-Auth: MTKj0qBrWPB8myu-Q5v3B7sD-1I
Message-ID: <CA+55aFxs9T4oTs5MR7rcnrBUeUgORXWWNx+T6x52ynqrN38C6Q@mail.gmail.com>
Subject: Re: printk: what is going on with additional newlines?
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        Pavel Machek <pavel@ucw.cz>,
        Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
        Petr Mladek <pmladek@suse.com>, Jan Kara <jack@suse.cz>,
        Andrew Morton <akpm@linux-foundation.org>,
        Jiri Slaby <jslaby@suse.com>, Andreas Mohr <andi@lisas.de>,
        Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, Aug 29, 2017 at 4:50 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> What about using the seq_buf*() then?

They do have the nice property that because we use them for various
/proc files, there are some helper functions in addition to just the
puts/printt/vprintf.

Ie seq_buf_putmem_hex().

And yeah, you can just do

        char buffer[80];
        struct seq_buf s;

        seq_buf_init(&s, buffer, sizeof(buffer));

if you want to use a stack buffer for a single line.

          Linus