From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758959Ab2EIXCm (ORCPT ); Wed, 9 May 2012 19:02:42 -0400 Received: from mail-pz0-f46.google.com ([209.85.210.46]:40874 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755382Ab2EIXCk (ORCPT ); Wed, 9 May 2012 19:02:40 -0400 MIME-Version: 1.0 In-Reply-To: References: <1336004953.4240.9.camel@mop> <1336475689.1179.12.camel@mop> <1336571457.30189.29.camel@joe2Laptop> Date: Wed, 9 May 2012 16:02:40 -0700 X-Google-Sender-Auth: 0TeO5lnxf72QtfJVdZJm3wpe99Q Message-ID: Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer From: Yinghai Lu To: Kay Sievers Cc: Joe Perches , Linus Torvalds , Sasha Levin , Greg Kroah-Hartmann , 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 Wed, May 9, 2012 at 7:37 AM, Kay Sievers wrote: > >> Changing printk semantics and trying to stabilize >> printk message content are bad ideas though. > > Again, nobody talks about content of here. printk_time=1 does not work anymore with this patch on serial console. but dmesg still have that time printout. Yinghai