Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755005AbcJGXKL (ORCPT ); Fri, 7 Oct 2016 19:10:11 -0400 Received: from mail-wm0-f46.google.com ([74.125.82.46]:37313 "EHLO mail-wm0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752652AbcJGXKB (ORCPT ); Fri, 7 Oct 2016 19:10:01 -0400 MIME-Version: 1.0 In-Reply-To: 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:09:51 -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: 617 Lines: 14 On Fri, Oct 7, 2016 at 4:01 PM, Tony Luck wrote: > 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. Retracted ... I'm sure that at some point in the past it happened like that ... but I just retested on 4.8 and the first message (with no "\n") showed up on the serial port just fine without some other message to push it out. When the next message came along, a "\n" was auto-inserted. -Tony