Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756453AbcJGXHu (ORCPT ); Fri, 7 Oct 2016 19:07:50 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:38360 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753440AbcJGXHm (ORCPT ); Fri, 7 Oct 2016 19:07:42 -0400 MIME-Version: 1.0 In-Reply-To: <1475876667.1945.28.camel@perches.com> References: <1475870688.1945.13.camel@perches.com> <1475871538.1945.15.camel@perches.com> <1475872401.1945.17.camel@perches.com> <1475876667.1945.28.camel@perches.com> From: Tony Luck Date: Fri, 7 Oct 2016 16:01:20 -0700 Message-ID: Subject: Re: [GIT PULL] trivial for 4.9 To: Joe Perches Cc: Linus Torvalds , Jiri Kosina , Colin Ian King , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 250 Lines: 7 What if there isn't a "next printk" call for hours, or days? That poor little message without a "\n" will sit in the kernel buffers, and the user who might want to see the message can't, until some unrelated thing happens to print something. -Tony