Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932316AbVLAQZx (ORCPT ); Thu, 1 Dec 2005 11:25:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932320AbVLAQZx (ORCPT ); Thu, 1 Dec 2005 11:25:53 -0500 Received: from rtr.ca ([64.26.128.89]:26786 "EHLO mail.rtr.ca") by vger.kernel.org with ESMTP id S932318AbVLAQZw (ORCPT ); Thu, 1 Dec 2005 11:25:52 -0500 Message-ID: <438F240F.2020300@rtr.ca> Date: Thu, 01 Dec 2005 11:25:51 -0500 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051013 Debian/1.7.12-1ubuntu1 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Linus Torvalds Cc: linux-kernel@vger.kernel.org Subject: Re: [PATCH] Fix bytecount result from printk() References: <438F1D05.5020004@rtr.ca> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 728 Lines: 18 Linus Torvalds wrote: > > On Thu, 1 Dec 2005, Mark Lord wrote: > >>On a related note, WHY does the LOG LEVEL format <6> not get >>interpreted correctly for the first printk() after an oops report? > > It never gets interpreted except at the behinning of a line. Sounds like > the oops report perhaps prints a " " without a newline or something at the > end, so that the next message after that isn't a new line? The oops report always ends with a simple newline: printk("\n"); - 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/