From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751431AbdIQJbz (ORCPT ); Sun, 17 Sep 2017 05:31:55 -0400 Received: from mail-pf0-f172.google.com ([209.85.192.172]:50016 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750803AbdIQJbx (ORCPT ); Sun, 17 Sep 2017 05:31:53 -0400 X-Google-Smtp-Source: ADKCNb6hvB6aODcmXBBxos3SXEsWxsI8zN8JSr8l+JVcHOZEWLAIkaBn/E5iLWR+f5DxxKcxks2pHQ== Date: Sun, 17 Sep 2017 18:27:04 +0900 From: Sergey Senozhatsky To: Petr Mladek Cc: Sergey Senozhatsky , Sergey Senozhatsky , Joe Perches , Steven Rostedt , Linus Torvalds , Pavel Machek , Jan Kara , Andrew Morton , Jiri Slaby , Andreas Mohr , Tetsuo Handa , Linux Kernel Mailing List Subject: Re: printk: what is going on with additional newlines? Message-ID: <20170917092704.GB512@tigerII.localdomain> References: <1504057959.2786.4.camel@perches.com> <20170830022528.GA17968@jagdpanzerIV.localdomain> <1504060296.2786.8.camel@perches.com> <20170830024703.GA17175@jagdpanzerIV.localdomain> <20170905094452.GE8741@pathway.suse.cz> <20170905095900.GC2066@jagdpanzerIV.localdomain> <20170905122154.GG8741@pathway.suse.cz> <20170905134228.GE521@jagdpanzerIV.localdomain> <20170906075554.GI8741@pathway.suse.cz> <20170917062608.GA512@tigerII.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170917062608.GA512@tigerII.localdomain> User-Agent: Mutt/1.9.0 (2017-09-02) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On (09/17/17 15:26), Sergey Senozhatsky wrote: [..] > > Anyway, it seems that we will need to update all the tools > > for the different time stamps, see > > https://lkml.kernel.org/r/1504613201-23868-1-git-send-email-prarit@redhat.com > > Then we will be more clever how painful it is. may be we can store that "really helpful different timestamps" in "extended data"? IOW, as part of message text? -ss