From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751419AbdIACE3 (ORCPT ); Thu, 31 Aug 2017 22:04:29 -0400 Received: from smtprelay0038.hostedemail.com ([216.40.44.38]:41687 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750996AbdIACE2 (ORCPT ); Thu, 31 Aug 2017 22:04:28 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::::::::::::::::::,RULES_HIT:41:355:379:541:599:973:981: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:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3870:3871:3873:3874:4321:4641:5007:6691:10004:10400:10848:11232:11658:11914:12740:12760:12895:13069:13311:13357:13439:14659:14721:21080:21088:21326:21433:21627:30012:30054:30060:30090:30091,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:1,LUA_SUMMARY:none X-HE-Tag: hands72_43cf2350a5629 X-Filterd-Recvd-Size: 2065 Message-ID: <1504231464.2786.52.camel@perches.com> Subject: Re: printk: what is going on with additional newlines? From: Joe Perches To: Sergey Senozhatsky , Pavel Machek Cc: Linus Torvalds , Sergey Senozhatsky , Petr Mladek , Steven Rostedt , Jan Kara , Andrew Morton , Jiri Slaby , Andreas Mohr , Tetsuo Handa , Linux Kernel Mailing List Date: Thu, 31 Aug 2017 19:04:24 -0700 In-Reply-To: <20170901014012.GA814@jagdpanzerIV.localdomain> References: <20170815025625.1977-1-sergey.senozhatsky@gmail.com> <20170828090521.GA25025@amd> <20170829202447.GA20829@amd> <20170901014012.GA814@jagdpanzerIV.localdomain> 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 Fri, 2017-09-01 at 10:40 +0900, Sergey Senozhatsky wrote: > On (08/29/17 22:24), Pavel Machek wrote: > > > > 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? [] > > You are welcome not add checkpatch rules to prevent such code from being > > merged... Pavel, what does this mean? > well... just a note, I personally developed a new habit - use > pr_err/pr_cont/etc macros instead of explicit printk(KERN_FOO "..."). > may be this can work for you. and we _probably_ need to advertise > pr_foo() more. As well as convert the macros to functions to save some .text too.