From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760699Ab2EKPrn (ORCPT ); Fri, 11 May 2012 11:47:43 -0400 Received: from mail-wg0-f42.google.com ([74.125.82.42]:33503 "EHLO mail-wg0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760340Ab2EKPrm (ORCPT ); Fri, 11 May 2012 11:47:42 -0400 MIME-Version: 1.0 In-Reply-To: References: <1336475689.1179.12.camel@mop> <1336571457.30189.29.camel@joe2Laptop> <20120509230649.GA10695@kroah.com> <1336617045.25027.2.camel@mop> <20120511151944.GA6990@kroah.com> From: Linus Torvalds Date: Fri, 11 May 2012 08:47:19 -0700 X-Google-Sender-Auth: 98sdsPCbv0SCmmF1oYiwM7jUwBE Message-ID: Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer To: Kay Sievers Cc: Greg KH , Sasha Levin , Yinghai Lu , Joe Perches , Ingo Molnar , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 11, 2012 at 8:40 AM, Kay Sievers wrote: > > Should we just pad the multi-newline-in-one-record output with 15 > spaces when printk_time is on? Yeah, I think that would be the nicest thing. Btw, I'd also *love* to see some model (eventually - not necessarily now) where we could have the option of the time printouts being a bit different (rather than just on/off). It would be very nice if we had "relative" time printouts for events close together, so the rule could be something like: - if time is same as last line, pad with empty - if time is more than a minute from last one, show an absolute value of dd hh:mm:ss - otherwise, show a relative value of +ss.mmmmmm So the on/off choice could be on/off/relative. Hmm? Linus