From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751373AbdH2RKj (ORCPT ); Tue, 29 Aug 2017 13:10:39 -0400 Received: from smtprelay0210.hostedemail.com ([216.40.44.210]:51717 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751066AbdH2RKi (ORCPT ); Tue, 29 Aug 2017 13:10:38 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::::::::,RULES_HIT:41:355:379:541:599:800:960:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1539:1593:1594:1711:1730:1747:1777:1792:2393:2553:2559:2562:2828:2898:3138:3139:3140:3141:3142:3309:3352:3622:3867:3868:3870:3871:3872:3873:3874:4250:4321:4641:5007:9040:10004:10400:10848:11232:11658:11914:12296:12740:12760:12895:13069:13311:13357:13439:14180:14181:14659:14721:21060:21080:21088:21627,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:2,LUA_SUMMARY:none X-HE-Tag: linen38_5c7b65e16d41b X-Filterd-Recvd-Size: 2036 Message-ID: <1504026634.2040.27.camel@perches.com> Subject: Re: printk: what is going on with additional newlines? From: Joe Perches To: Linus Torvalds , Pavel Machek Cc: Sergey Senozhatsky , Petr Mladek , Steven Rostedt , Jan Kara , Andrew Morton , Jiri Slaby , Andreas Mohr , Tetsuo Handa , Linux Kernel Mailing List , Sergey Senozhatsky Date: Tue, 29 Aug 2017 10:10:34 -0700 In-Reply-To: References: <20170815025625.1977-1-sergey.senozhatsky@gmail.com> <20170828090521.GA25025@amd> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.6-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2017-08-29 at 09:48 -0700, Linus Torvalds wrote: > On Mon, Aug 28, 2017 at 2:05 AM, Pavel Machek wrote: > > Hi! > > > > In 4.13-rc, printk("foo"); printk("bar"); seems to produce > > foo\nbar. That's... quite surprising/unwelcome. What is going on > > there? Are timestamps responsible? > > No. > > It's actively trying to treach you not to do shit. > > If you want to continue a line, you NEED to use KERN_CONT. > > That has always been true. It hasn't always been enforced, though. That's simply false. It was never true until you made it a requirement. (it's not a bad requirement, but it did change behavior) It was just unfortunate there were( and still are) many cases that needed updating.