From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755473AbcJLQRL (ORCPT ); Wed, 12 Oct 2016 12:17:11 -0400 Received: from smtprelay0016.hostedemail.com ([216.40.44.16]:47494 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753498AbcJLQQz (ORCPT ); Wed, 12 Oct 2016 12:16:55 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::,RULES_HIT:41:355:379:541:599:960:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1539:1593:1594:1711:1714:1730:1747:1777:1792:2198:2199:2393:2559:2562:2731:2828:3138:3139:3140:3141:3142:3351:3622:3865:3867:3868:3872:3873:3874:4321:5007:7903:10004:10400:10848:11232:11658:11914:12296:12533:12663:12740:12760:13069:13311:13357:13439:14659:14721:21080:21220:21433:30054:30060:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:1,LUA_SUMMARY:none X-HE-Tag: sleep55_8c1c874acd541 X-Filterd-Recvd-Size: 1589 Message-ID: <1476288961.16823.11.camel@perches.com> Subject: Re: linux.git: printk() problem From: Joe Perches To: Linus Torvalds , Tetsuo Handa Cc: Linux Kernel Mailing List Date: Wed, 12 Oct 2016 09:16:01 -0700 In-Reply-To: References: <201610122230.DID43237.FSOHFFQOJOtVML@I-love.SAKURA.ne.jp> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.22.0-2ubuntu1 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 Wed, 2016-10-12 at 08:47 -0700, Linus Torvalds wrote: < We'll see. But the other issues are easily fixed by just adding > KERN_CONT where appropriate. It was actually very much what you were > supposed to do before too, if only as a marker to others that "yes, > I'm actually doing this, and no, I'm not supposed to have a log level" > (but with the new world order you actually *can* combine KERN_CONT > with a loglevel, so that if the beginning od the line got flushed, the > continuation can still be printed with the right log level). I think that might not be a good idea. Anything that uses a KERN_CONT with a new log level might as well be converted into multiple printks.