From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751034AbdIREmr (ORCPT ); Mon, 18 Sep 2017 00:42:47 -0400 Received: from mail-pg0-f45.google.com ([74.125.83.45]:46324 "EHLO mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750897AbdIREmq (ORCPT ); Mon, 18 Sep 2017 00:42:46 -0400 X-Google-Smtp-Source: AOwi7QCqCeZz44sME6wbcZhgEHhi4MEeqmrLINhXzavDeLHMszzzQZZkzsXOlOAZb13UZM4gSLGPXA== Date: Mon, 18 Sep 2017 13:42:40 +0900 From: Sergey Senozhatsky To: Joe Perches Cc: Sergey Senozhatsky , Linus Torvalds , Sergey Senozhatsky , Petr Mladek , Steven Rostedt , 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: <20170918044240.GE3161@jagdpanzerIV.localdomain> References: <20170905134228.GE521@jagdpanzerIV.localdomain> <20170906075554.GI8741@pathway.suse.cz> <20170917062608.GA512@tigerII.localdomain> <20170918004641.GA3161@jagdpanzerIV.localdomain> <1505701349.12022.1.camel@perches.com> <20170918024111.GC3161@jagdpanzerIV.localdomain> <1505702746.12022.2.camel@perches.com> <20170918025455.GD3161@jagdpanzerIV.localdomain> <1505704058.12022.4.camel@perches.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1505704058.12022.4.camel@perches.com> 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 20:07), Joe Perches wrote: > On Mon, 2017-09-18 at 11:55 +0900, Sergey Senozhatsky wrote: > > Try git grep KERN_SOH. > > > > what for? > > Did you read your own email? > > > printk(KERN_SOH_ASCII %d " foo bar / %s %s\n", "foo", "bar"); > > _nothing_ looks like that. OK... got it. I obviously meant the way we treat the prefix - KERN_SOH_ASCII and int loglevel that we store in msg->level - and not the way the prefix actually looks (KERN_SOH %c). I thought that was kinda clear. anyway, the point of my email was completely different. sorry if that confused you, or anybody else. > It wouldn't even compile. well, don't try to compile my emails ;) -ss