Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760882Ab2EJStq (ORCPT ); Thu, 10 May 2012 14:49:46 -0400 Received: from mail-yx0-f174.google.com ([209.85.213.174]:43732 "EHLO mail-yx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760449Ab2EJStp convert rfc822-to-8bit (ORCPT ); Thu, 10 May 2012 14:49:45 -0400 MIME-Version: 1.0 In-Reply-To: References: <1336004953.4240.9.camel@mop> <1336475689.1179.12.camel@mop> <20120509070710.GA29981@gmail.com> <1336611278.728.9.camel@mop> <1336667984.947.24.camel@mop> Date: Thu, 10 May 2012 11:49:44 -0700 Message-ID: Subject: Re: [PATCH RESEND 1/3] printk: convert byte-buffer to variable-length record buffer From: Tony Luck To: Linus Torvalds Cc: Kay Sievers , Ingo Molnar , Jonathan Corbet , Sasha Levin , Greg Kroah-Hartmann , linux-kernel@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 898 Lines: 19 On Thu, May 10, 2012 at 9:47 AM, Linus Torvalds wrote: > ? This is often useful for having loops that print out individual > entries all on the same line - print all of them without the '\n'. Though it is a pain when people do this and the output from each iteration of the loop gets interleaved with other printk() output. Perhaps it is OK to do multiple printk() calls in initialization code where it kernel is mostly single threaded. But it should be avoided in "oh dear, something bad happened" bits of code (in case the badness isn't localized and all the other cpus are spitting out partial messages too). -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/